Triple
T35497352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huastecan languages |
E1025903
|
entity |
| Predicate | statusOfChicomuceltec |
P200397
|
FINISHED |
| Object | extinct |
—
|
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: extinct | Statement: [Huastecan languages, statusOfChicomuceltec, extinct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfChicomuceltec Context triple: [Huastecan languages, statusOfChicomuceltec, extinct]
-
A.
statusInMexico
Indicates the legal or social status that an entity holds within the context of Mexico.
-
B.
statusInChile
Indicates the legal, social, or operational status that an entity holds specifically within the context of Chile.
-
C.
statusRelativeToAztecs
Indicates the nature or condition of something in relation to the Aztecs, such as its standing, role, or classification with respect to them.
-
D.
NohochMul_statusInQuintanaRoo
Indicates that the site or structure Nohoch Mul holds a particular official or contextual status within the region of Quintana Roo.
-
E.
statusInPeru
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Peru.
- F. None of above. chosen
Provenance (4 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
| PDg | Predicate description generation | batch_69ff878e8334819097e3c4bb5ca6ffa5 |
completed | May 9, 2026, 7:14 p.m. |
Created at: May 3, 2026, 4:04 p.m.