Triple
T5386658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Ossetian language authorities |
E120217
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ossetian-language organization |
C12587
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Ossetian-language organization Context triple: [North Ossetian language authorities, instanceOf, Ossetian-language organization]
-
A.
Crimean Tatar organization
A Crimean Tatar organization is a formal group or institution established by or for Crimean Tatars to represent their interests, preserve their culture and language, and address social, political, or community issues.
-
B.
Esperanto organization
An Esperanto organization is a group or institution dedicated to promoting, teaching, using, and supporting the international language Esperanto and its associated culture and ideals.
-
C.
Northwest Caucasian people
Northwest Caucasian people are an indigenous group of ethnic communities native to the northwestern Caucasus region, characterized by distinct languages, cultures, and historical traditions.
-
D.
language revitalization organization
chosen
A language revitalization organization is a group dedicated to preserving, strengthening, and promoting the use of endangered or marginalized languages through education, community programs, documentation, and advocacy.
-
E.
Northwest Caucasian language
A Northwest Caucasian language is a member of a small family of indigenous languages spoken in the northwestern Caucasus region, characterized by complex consonant systems, minimal vowel inventories, and rich verbal morphology.
- F. None of above.
Provenance (1 batch)
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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
Created at: March 20, 2026, 2:03 p.m.