Triple
T12320407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braldu Valley |
E293712
|
entity |
| Predicate | languageRegion |
P387
|
FINISHED |
| Object | Balti language |
E375700
|
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: Balti language | Statement: [Braldu Valley, languageRegion, Balti language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Balti language Context triple: [Braldu Valley, languageRegion, Balti language]
-
A.
Balti language
chosen
The Balti language is a Tibetic language spoken primarily in the Baltistan region of northern Pakistan, known for preserving many archaic features of Classical Tibetan.
-
B.
Bariai language
The Bariai language is an Austronesian language spoken by the Bariai people of New Britain in Papua New Guinea.
-
C.
Jur Beli language
Jur Beli is a lesser-known Nilotic language spoken by the Jur Beli people of South Sudan.
-
D.
Boro language
Boro language is a Tibeto-Burman language spoken primarily by the Boro people of Assam in northeastern India.
-
E.
Balantak language
The Balantak language is an Austronesian language spoken by the Balantak people of eastern Central Sulawesi, Indonesia.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f4c2b548190938fff9427f07dc7 |
completed | April 10, 2026, 6:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e8aa94881908e4c184062037ab5 |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:53 p.m.