Triple
T9669655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oghur languages |
E233992
|
entity |
| Predicate | statusOfChuvash |
P89515
|
FINISHED |
| Object | only surviving Oghur language |
—
|
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: only surviving Oghur language | Statement: [Oghur languages, statusOfChuvash, only surviving Oghur language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfChuvash Context triple: [Oghur languages, statusOfChuvash, only surviving Oghur language]
-
A.
statusInRussia
Indicates the legal, social, or operational condition or standing that something or someone has specifically within the context of Russia.
-
B.
statusInRussianEmpire
Indicates the legal or social standing an entity held within the political and administrative system of the Russian Empire.
-
C.
statusInCroatia
Indicates the legal, social, or official standing or condition that an entity holds within the context of Croatia.
-
D.
statusOfSakhalin
Indicates the current political, administrative, or territorial status or condition of Sakhalin in relation to a governing authority or jurisdiction.
-
E.
statusOfVilnius
Indicates the current political or administrative status or condition assigned to Vilnius.
- F. None of above. chosen
Provenance (4 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3ec17081908c2da74a1d1f49da |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:15 p.m.