Triple
T2648377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlacopan polity |
E53836
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Tacuba |
E60721
|
NE 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: Tacuba | Statement: [Tlacopan polity, alsoKnownAs, Tacuba]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tacuba Context triple: [Tlacopan polity, alsoKnownAs, Tacuba]
-
A.
Tacuba
chosen
Tacuba is a historic neighborhood in Mexico City known for its colonial-era architecture and role as a former pre-Hispanic town.
-
B.
Tecali
Tecali is a Mexican town renowned for its traditional crafts, particularly the production of Talavera pottery and stonework.
-
C.
Tuxpan
Tuxpan is a town and municipality in the Mexican state of Nayarit, known for its agricultural economy and traditional cultural festivals.
-
D.
Tuxpan
Tuxpan is a port city in the Mexican state of Veracruz, known for its Gulf Coast location and historical role as a departure point in the Cuban Revolution.
-
E.
Topete
Topete is a Spanish surname associated with notable figures such as admiral Pascual Cervera y Topete.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91b4b3c81908571e85a1621dfc5 |
completed | March 7, 2026, 7:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b0fc4137cc8190a67bf8be5d8e062c |
completed | March 11, 2026, 5:23 a.m. |
Created at: March 6, 2026, 9:53 p.m.