Triple

T32155472
Position Surface form Disambiguated ID Type / Status
Subject Tacuba, Mexico City E821276 entity
Predicate wasKnownInPreHispanicTimesAs P173019 FINISHED
Object Tlacopan NE NERFINISHED

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: Tlacopan | Statement: [Tacuba, Mexico City, wasKnownInPreHispanicTimesAs, Tlacopan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasKnownInPreHispanicTimesAs
Context triple: [Tacuba, Mexico City, wasKnownInPreHispanicTimesAs, Tlacopan]
  • A. preColumbianNameOf chosen
    Indicates that the object is the name used for the subject in the pre-Columbian period.
  • B. isPreColumbian
    Indicates that something existed, occurred, or was created in the Americas before the arrival of Christopher Columbus in 1492.
  • C. hasPreColumbianCulture
    Indicates that an entity possesses or is associated with a culture that existed in the Americas before the arrival of Columbus and European contact.
  • D. preColumbianSettlement
    Indicates that an entity is a human settlement that existed in a region before the arrival of Christopher Columbus and subsequent European contact.
  • E. historicalNameInSpanish
    Indicates that an entity is known or referred to by a particular historical name when expressed in the Spanish language.
  • 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_69f34905e098819082191a6922a6d607 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b9eefa3c81909dea4f3e71b6a929 completed May 3, 2026, 2:58 a.m.
PD Predicate disambiguation batch_69f6b3a970b0819090c6473844ffa8e3 completed May 3, 2026, 2:32 a.m.
Created at: May 1, 2026, 12:32 a.m.