Triple
T3728430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabriz dialect |
E79004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Azerbaijani |
C14002
|
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 Azerbaijani Context triple: [Tabriz dialect, instanceOf, regional variety of Azerbaijani]
-
A.
Kurdish dialect
A Kurdish dialect is a regional or social variety of the Kurdish language characterized by distinct phonological, lexical, and grammatical features shared by a specific Kurdish-speaking community.
-
B.
Azerbaijani-American
An Azerbaijani-American is a person in the United States who has full or partial Azerbaijani ancestry, heritage, or cultural ties.
-
C.
Northwest Iranian language
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.
-
D.
regional variety of Bengali
A regional variety of Bengali is a localized form of the Bengali language characterized by distinct phonological, lexical, and sometimes grammatical features associated with a specific geographic area or speech community.
-
E.
variety of the Albanian language
A variety of the Albanian language is a distinct, systematically patterned form of Albanian—such as a dialect, sociolect, or regional speech form—characterized by unique phonological, lexical, and grammatical features within the broader Albanian linguistic continuum.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:34 p.m.