Triple
T20899415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shor language |
E514629
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Altai 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: Altai language | Statement: [Shor language, closelyRelatedTo, Altai language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Altai language Context triple: [Shor language, closelyRelatedTo, Altai language]
-
A.
Altai language
chosen
The Altai language is a Turkic language spoken primarily in Russia’s Altai Republic and surrounding regions by the indigenous Altai people.
-
B.
Chulym language
The Chulym language is a critically endangered Turkic language spoken by a small indigenous community in Siberia, Russia.
-
C.
Khakas language
Khakas language is a Turkic language spoken primarily by the Khakas people in the Republic of Khakassia in south-central Siberia, Russia.
-
D.
Tsakhur language
The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
-
E.
Sibe language
Sibe language is a modern Tungusic language spoken primarily by the Sibe people in Xinjiang, China, and is closely related to Manchu.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8f92bd88190b59b2131ad1d9aa1 |
completed | April 21, 2026, 3:03 a.m. |
Created at: April 16, 2026, 12:47 p.m.