Triple
T21201306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babolki dialect |
E522460
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Mazanderani |
C5771
|
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: regional variety of Mazanderani Context triple: [Babolki dialect, instanceOf, regional variety of Mazanderani]
-
A.
regional variety of Azerbaijani
A regional variety of Azerbaijani is a geographically or socially localized form of the Azerbaijani language characterized by distinct phonological, lexical, and sometimes grammatical features.
-
B.
Northwest Iranian language
chosen
A Northwest Iranian language is a member of the western branch of the Iranian languages spoken primarily in regions of northwestern Iran and neighboring areas, characterized by shared phonological, lexical, and grammatical features distinct from Southwest Iranian languages.
-
C.
regional variety of Lezgian
A regional variety of Lezgian is a geographically distinct form of the Lezgian language characterized by unique phonological, lexical, and grammatical features shared by speakers in a particular area.
-
D.
regional variety of the Kumyk language
A regional variety of the Kumyk language is a geographically defined form of Kumyk that exhibits distinct phonological, lexical, or grammatical features while remaining mutually intelligible with other Kumyk dialects.
-
E.
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.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:18 p.m.