Triple
T4338191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olenyok |
E97513
|
entity |
| Predicate | ethnicComposition |
P1898
|
FINISHED |
| Object | Yakut |
E233986
|
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: Yakut | Statement: [Olenyok, ethnicComposition, Yakut]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yakut Context triple: [Olenyok, ethnicComposition, Yakut]
-
A.
Yakut
chosen
Yakut is a Turkic language spoken primarily in the Sakha Republic (Yakutia) in northeastern Siberia, Russia.
-
B.
Yura
Yura is a common Slavic diminutive form of the male given name Yuri (or Yuriy), often used as a familiar or affectionate nickname.
-
C.
Ivilyuat
Ivilyuat is the endonym used by the Cahuilla people for their native Uto-Aztecan language traditionally spoken in Southern California.
-
D.
Aka-Kol
Aka-Kol is an extinct Great Andamanese language once spoken by the indigenous Kol people of the Andaman Islands in India.
-
E.
Yakutiye
Yakutiye is a central district and municipality of the city of Erzurum in eastern Turkey, serving as one of its main administrative and urban areas.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3516c621881909f094d040d4805e9 |
completed | March 12, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5e4f6643081909a2ad9a7d057ea2a |
completed | March 14, 2026, 10:45 p.m. |
Created at: March 12, 2026, 11:14 p.m.