Triple
T34837468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | archaeological zone of Tlatelolco |
E1004238
|
entity |
| Predicate | languageOfHistoricPopulation |
P1434
|
FINISHED |
| Object | Nahuatl |
—
|
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: Nahuatl | Statement: [archaeological zone of Tlatelolco, languageOfHistoricPopulation, Nahuatl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfHistoricPopulation Context triple: [archaeological zone of Tlatelolco, languageOfHistoricPopulation, Nahuatl]
-
A.
historicalLanguageOfBearers
Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
-
B.
historicalLanguageGroup
Indicates that two or more entities belong to the same historically defined language group or family, based on shared linguistic ancestry or development.
-
C.
languageOfHistoricName
Indicates the language in which a historic or former name of an entity is expressed.
-
D.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
E.
historicallySpokenIn
chosen
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a009273634c8190b5b9c87053b56760 |
completed | May 10, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_6a0092171230819096e4274dd97e0410 |
completed | May 10, 2026, 2:11 p.m. |
Created at: May 3, 2026, 4 p.m.