Triple
T13923746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandeali |
E334808
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Kangri language |
E536085
|
NE FINISHED |
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: Kangri language | Statement: [Mandeali, closelyRelatedTo, Kangri language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kangri language Context triple: [Mandeali, closelyRelatedTo, Kangri language]
-
A.
Kangri language
chosen
Kangri language is an Indo-Aryan language spoken primarily in the Kangra region of Himachal Pradesh, India, and surrounding areas.
-
B.
Kangjia language
The Kangjia language is a lesser-known Mongolic language spoken by the Kangjia people in parts of northwestern China.
-
C.
Kumaoni language
Kumaoni language is an Indo-Aryan language of the Central Pahari group spoken primarily in the Kumaon region of Uttarakhand, India.
-
D.
Thakri language
Thakri is a lesser-known Southern Indo-Aryan language spoken by regional communities in the Indian subcontinent.
-
E.
Khetrani language
Khetrani language is an Indo-Aryan language spoken by the Khetrani people, primarily in parts of Balochistan, Pakistan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa6cd9881908f652538f4613f37 |
completed | April 14, 2026, 11:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7ce7ecb488190b96f67cad4b91968 |
completed | May 3, 2026, 10:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.