Triple
T37317233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarascans |
E926369
|
entity |
| Predicate | capitalOfPrehispanicState |
P140106
|
FINISHED |
| Object | Tzintzuntzan |
—
|
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: Tzintzuntzan | Statement: [Tarascans, capitalOfPrehispanicState, Tzintzuntzan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfPrehispanicState Context triple: [Tarascans, capitalOfPrehispanicState, Tzintzuntzan]
-
A.
preColumbianCapitalCity
chosen
Indicates that a city served as a capital prior to the arrival of Columbus and European contact in the Americas.
-
B.
territorialCapital
Indicates that a location serves as the administrative or political capital of a defined territory or region.
-
C.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
D.
governingTerritorialCapital
Indicates that a territorial entity serves as the administrative or political capital for a governing body or jurisdiction.
-
E.
territorialCapitalFrom
Indicates that something serves as the capital of a specified territory or is derived from the territorial capital of that entity.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:16 p.m.