Triple
T21710050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matlatzinca language |
E535877
|
entity |
| Predicate | endangermentReason |
P106049
|
FINISHED |
| Object | language shift to Spanish |
—
|
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: language shift to Spanish | Statement: [Matlatzinca language, endangermentReason, language shift to Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endangermentReason Context triple: [Matlatzinca language, endangermentReason, language shift to Spanish]
-
A.
endangerment
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
B.
isEndangeredDueTo
chosen
Indicates that an entity is endangered as a result of the specific cause or factor represented by the related entity.
-
C.
conservationStatusReason
Indicates the justification or underlying factors explaining why an entity has been assigned a particular conservation status.
-
D.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
E.
extinctionReason
Indicates the cause or factor responsible for an entity’s extinction.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb5333c8481909d729fb3bc3c9bc5 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.