Triple

T5048175
Position Surface form Disambiguated ID Type / Status
Subject Texcoco E113717 entity
Predicate tributeShareInAlliance P20379 FINISHED
Object two-fifths of collected tribute (traditional account) LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: two-fifths of collected tribute (traditional account) | Statement: [Texcoco, tributeShareInAlliance, two-fifths of collected tribute (traditional account)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tributeShareInAlliance
Context triple: [Texcoco, tributeShareInAlliance, two-fifths of collected tribute (traditional account)]
  • A. tributeFrom chosen
    Indicates that one entity pays or provides tribute, often as a sign of submission or obligation, to another entity.
  • B. sharesUniverseWith
    Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
  • C. sharesAuthorWith
    Indicates that two entities have at least one author in common.
  • D. tributeTo
    Indicates that one entity is created, given, or dedicated as a mark of respect, admiration, or honor toward another entity.
  • E. sharesFeatureWith
    Indicates that two entities have at least one common attribute, property, or characteristic in common.
  • F. None of above.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69bd44391fc48190a311ce9c826c209b completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7401419081909ba62b9c27f770c4 completed March 20, 2026, 4:21 p.m.
PD Predicate disambiguation batch_69bd715479f08190933604aebd34414f completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:37 p.m.