Triple
T8819432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sela Pass |
E209863
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Tawang |
E215181
|
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: Tawang | Statement: [Sela Pass, connects, Tawang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tawang Context triple: [Sela Pass, connects, Tawang]
-
A.
Tawang
chosen
Tawang is a remote Himalayan town in northeastern India known for its large 17th-century Buddhist monastery and scenic mountain landscapes near the India–China border.
-
B.
Nishapuri
Nishapuri refers to the Iranian-origin Nishapurid dynasty from which the Nawabs of Awadh claimed descent.
-
C.
Nurpur
Nurpur is a historic town in the Kangra district of Himachal Pradesh, India, known for its ancient fort and temples amid scenic Himalayan foothills.
-
D.
Diphu
Diphu is a town in the Karbi Anglong district of Assam, India, known as an administrative and educational hub in the region.
-
E.
Damauli
Damauli is a town in central Nepal that serves as the administrative headquarters of Tanahun District and a key junction along major transport routes.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600e6e2881908934cbff0ab5d6fd |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cfa05742948190bcec72a080f6837a |
completed | April 3, 2026, 11:11 a.m. |
Created at: March 30, 2026, 6:46 p.m.