Triple
T20632951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tepiman languages |
E507002
|
entity |
| Predicate | languageFamilyOf |
P35117
|
FINISHED |
| Object | Eudeve language |
—
|
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: Eudeve language | Statement: [Tepiman languages, languageFamilyOf, Eudeve language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eudeve language Context triple: [Tepiman languages, languageFamilyOf, Eudeve language]
-
A.
Eudeve language
chosen
The Eudeve language is an extinct Uto-Aztecan language once spoken by the Eudeve people in northern Mexico.
-
B.
Ede language
Ede language is a cluster of closely related Yoruba dialects spoken primarily by the Ede people in parts of West Africa, especially in Benin and neighboring regions.
-
C.
Kavelchadom language
The Kavelchadom language is a lesser-known indigenous Yuman language historically spoken in the Lower Colorado River region of the southwestern United States and northern Mexico.
-
D.
Endegen language
Endegen is an Ethiopian Semitic language belonging to the Gurage branch, spoken by a small community in central Ethiopia.
-
E.
Saraveca language
The Saraveca language is an extinct Arawakan language once spoken in Bolivia, known from very limited historical documentation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0bdcd88190a59d68e03370b271 |
completed | April 20, 2026, 10:47 p.m. |
Created at: April 16, 2026, 11:42 a.m.