Triple
T21718101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chambeali language |
E536083
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Chamiyali |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Chamiyali | Statement: [Chambeali language, hasAlternativeName, Chamiyali]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chamiyali Context triple: [Chambeali language, hasAlternativeName, Chamiyali]
-
A.
Chamiyali
chosen
Chamiyali is an Indo-Aryan language variety spoken in the Chamba region of Himachal Pradesh, India.
-
B.
Chaam
Chaam is a village in the Dutch province of North Brabant, known for its rural character and historic ties to the Baronie of Breda.
-
C.
Chakia
Chakia is a town in the East Champaran district of the Indian state of Bihar, known primarily as a local administrative and market center for the surrounding rural region.
-
D.
Chambiali
Chambiali is an Indo-Aryan language variety spoken in parts of the Himachal Pradesh region of northern India.
-
E.
Chamalin
Chamalin is an alternative name for the Chamalal language, a Northeast Caucasian language spoken by the Chamalal people in Dagestan, Russia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96babdc81908226ec043dbe7431 |
completed | April 27, 2026, 9:47 p.m. |
Created at: April 16, 2026, 6:47 p.m.