Triple
T5361610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeastern Turkic |
E103033
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Tofalar language |
E514630
|
NE 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: Tofalar language | Statement: [Northeastern Turkic, hasMember, Tofalar language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tofalar language Context triple: [Northeastern Turkic, hasMember, Tofalar language]
-
A.
Tofa language
chosen
Tofa is a critically endangered Turkic language traditionally spoken by the Tofa (Tofalars) people of south-central Siberia in Russia.
-
B.
Towa language
Towa is a Native American language spoken by the Towa (Jemez) people of New Mexico and is part of the Puebloan language family.
-
C.
Tanema language
Tanema is a nearly extinct Oceanic language once spoken on Vanikoro Island in the Temotu Province of the Solomon Islands.
-
D.
Tokodede language
Tokodede is an Austronesian language spoken primarily in the Liquiçá region of northwestern East Timor.
-
E.
Opata language
The Opata language is an extinct Uto-Aztecan language once spoken by the Opata people of northern Mexico, particularly in the present-day state of Sonora.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865a0bb081909579cfe7c7974075 |
completed | March 20, 2026, 5:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf291c89c8819084b9305c3bddc3c0 |
completed | March 21, 2026, 11:26 p.m. |
Created at: March 20, 2026, 2:02 p.m.