concrete.metadata package

class concrete.metadata.ttypes.AnnotationMetadata(tool=None, timestamp=None, digest=None, dependencies=None, kBest=1)

Bases: object

Metadata associated with an annotation or a set of annotations,

that identifies where those annotations came from.

Attributes:

- tool: The name of the tool that generated this annotation.

- timestamp: The time at which this annotation was generated (in unix time

UTC – i.e., seconds since January 1, 1970).

- digest: A Digest, carrying over any information the annotation metadata

wishes to carry over.

- dependencies: The theories that supported this annotation.

An empty field indicates that the theory has no

dependencies (e.g., an ingester).

- kBest: An integer that represents a ranking for systems

that output k-best lists.

For systems that do not output k-best lists,

the default value (1) should suffice.

read(iprot)

validate()

write(oprot)

class concrete.metadata.ttypes.CommunicationMetadata(tweetInfo=None, emailInfo=None, nitfInfo=None)

Bases: object

Metadata specific to a particular Communication object.

This might include corpus-specific metadata (from the Twitter API),

attributes associated with the Communication (the author),

or other information about the Communication.

Attributes:

- tweetInfo: Extra information for communications where kind==TWEET:

Information about this tweet that is provided by the Twitter

API. For information about the Twitter API, see:

https://dev.twitter.com/docs/platform-objects

- emailInfo: Extra information for communications where kind==EMAIL

- nitfInfo: Extra information that may come from the NITF

(News Industry Text Format) schema. See ‘nitf.thrift’.

read(iprot)

validate()

write(oprot)

class concrete.metadata.ttypes.Digest(bytesValue=None, int64Value=None, doubleValue=None, stringValue=None, int64List=None, doubleList=None, stringList=None)

Bases: object

Analytic-specific information about an attribute or edge. Digests

are used to combine information from multiple sources to generate a

unified value. The digests generated by an analytic will only ever

be used by that same analytic, so analytics can feel free to encode

information in whatever way is convenient.

Attributes:

- bytesValue: The following fields define various ways you can store the

digest data (for convenience). If none of these meets your

needs, then serialize the digest to a byte sequence and store it

in bytesValue.

- int64Value

- doubleValue

- stringValue

- int64List

- doubleList

- stringList

read(iprot)

validate()

write(oprot)

class concrete.metadata.ttypes.TheoryDependencies(sectionTheoryList=None, sentenceTheoryList=None, tokenizationTheoryList=None, posTagTheoryList=None, nerTagTheoryList=None, lemmaTheoryList=None, langIdTheoryList=None, parseTheoryList=None, dependencyParseTheoryList=None, tokenAnnotationTheoryList=None, entityMentionSetTheoryList=None, entitySetTheoryList=None, situationMentionSetTheoryList=None, situationSetTheoryList=None, communicationsList=None)

Bases: object

A struct that holds UUIDs for all theories that a particular

annotation was based upon (and presumably requires).

Producers of TheoryDependencies should list all stages that they

used in constructing their particular annotation. They do not,

however, need to explicitly label each stage; they can label

only the immediate stage before them.

Examples:

If you are producing a Tokenization, and only used the

SentenceSegmentation in order to produce that Tokenization, list

only the single SentenceSegmentation UUID in sentenceTheoryList.

In this example, even though the SentenceSegmentation will have

a dependency on some SectionSegmentation, it is not necessary

for the Tokenization to list the SectionSegmentation UUID as a

dependency.

If you are a producer of EntityMentions, and you use two

POSTokenTagging and one NERTokenTagging objects, add the UUIDs for

the POSTokenTagging objects to posTagTheoryList, and the UUID of

the NER TokenTagging to the nerTagTheoryList.

In this example, because multiple annotations influenced the

new annotation, they should all be listed as dependencies.

Attributes:

- sectionTheoryList

- sentenceTheoryList

- tokenizationTheoryList

- posTagTheoryList

- nerTagTheoryList

- lemmaTheoryList

- langIdTheoryList

- parseTheoryList

- dependencyParseTheoryList

- tokenAnnotationTheoryList

- entityMentionSetTheoryList

- entitySetTheoryList

- situationMentionSetTheoryList

- situationSetTheoryList

- communicationsList

read(iprot)

validate()

write(oprot)