Triple
T3653196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balti |
E77468
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Balti Tibetan |
E77468
|
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 Tibetan | Statement: [Balti, hasAlternativeName, Balti Tibetan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Balti Tibetan Context triple: [Balti, hasAlternativeName, Balti Tibetan]
-
A.
Tibetan
Tibetan is a Sino-Tibetan language spoken primarily in Tibet and surrounding Himalayan regions, serving as the liturgical language of Tibetan Buddhism and a key marker of Tibetan cultural identity.
-
B.
Garhwali
Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
-
C.
Dholuo
Dholuo is a Nilotic language spoken primarily by the Luo people of western Kenya and parts of Tanzania.
-
D.
Balti
chosen
Balti is a Tibetic language spoken primarily in the Baltistan region of northern Pakistan and parts of Ladakh, India.
-
E.
Gyel dialect
The Gyel dialect is a regional variety of the Berom language spoken by the Berom people of central Nigeria.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b805a48190a7bc230a382365d6 |
completed | March 8, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b44f4541dc8190b794eae019dcffbf |
completed | March 13, 2026, 5:54 p.m. |
Created at: March 8, 2026, 3:24 p.m.