Triple
T29042057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chibhali |
E738021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pahari-Potohari dialect |
C6020
|
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: Pahari-Potohari dialect Context triple: [Chibhali, instanceOf, Pahari-Potohari dialect]
-
A.
Punjabi dialect
chosen
A Punjabi dialect is a regional or social variety of the Punjabi language characterized by distinct pronunciation, vocabulary, and grammatical features used by specific communities within Punjabi-speaking areas.
-
B.
Rajasthani dialect
Rajasthani dialect is a regional linguistic variety spoken in the Indian state of Rajasthan, characterized by its distinct phonetics, vocabulary, and grammar that differentiate it from standard Hindi and other neighboring languages.
-
C.
Isnag dialect
The Isnag dialect is a variant of the Isnag language spoken by the Isnag people of northern Luzon in the Philippines, characterized by its distinct phonology, vocabulary, and grammatical features within the Northern Luzon language group.
-
D.
regional variety of Garhwali
A regional variety of Garhwali is a localized form of the Garhwali language distinguished by its unique phonological, lexical, and syntactic features specific to a particular area within the Garhwal region.
-
E.
Pulaar dialect
The Pulaar dialect is a regional variety of the Fula language spoken primarily by the Fula people in parts of West Africa, characterized by distinct phonological, lexical, and grammatical features.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:02 a.m.