Triple
T21201175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabari language |
E522456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Caspian language |
C44350
|
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: Caspian language Context triple: [Tabari language, instanceOf, Caspian language]
-
A.
Pamir language
The Pamir language is a group of Eastern Iranian languages spoken in the high-mountain Pamir region of Tajikistan, Afghanistan, and surrounding areas, characterized by significant diversity and archaic linguistic features.
-
B.
Hurro-Urartian language
A Hurro-Urartian language is a member of an extinct family of ancient Near Eastern languages, primarily known from cuneiform inscriptions of the Hurrians and Urartians in the second and first millennia BCE.
-
C.
Shastan language
The Shastan language is a group of closely related, now mostly extinct Native American languages once spoken by the Shasta and neighboring peoples of northern California and southern Oregon.
-
D.
Zaza–Gorani language
The Zaza–Gorani language is a proposed grouping of two closely related Northwestern Iranian languages, Zaza and Gorani, spoken primarily by ethnic Kurdish and related communities in eastern Turkey, northern Iraq, and western Iran.
-
E.
Elamite language
Elamite language is an extinct language isolate once spoken in the ancient kingdom of Elam in what is now southwestern Iran, known primarily from cuneiform inscriptions dating from the 3rd to 1st millennia BCE.
- F. None of above. chosen
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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:18 p.m.