Triple
T686585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilgit-Baltistan |
E13296
|
entity |
| Predicate | containsPeak |
P8205
|
FINISHED |
| Object | K2 |
E9638
|
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: K2 | Statement: [Gilgit-Baltistan, containsPeak, K2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: K2 Context triple: [Gilgit-Baltistan, containsPeak, K2]
-
A.
K2
chosen
K2 is the world’s second-highest mountain, a notoriously difficult and dangerous peak in the Karakoram range of the Himalayas.
-
B.
Tirich Mir
Tirich Mir is a towering mountain peak in Pakistan’s Chitral region, renowned as the highest summit in the Hindu Kush range.
-
C.
Gasherbrum I
Gasherbrum I is one of the world’s fourteen eight-thousanders, a major peak of the Karakoram range on the Pakistan–China border and among the highest mountains on Earth.
-
D.
Kangchenjunga
Kangchenjunga is the world’s third-highest mountain, a massive peak in the eastern Himalayas on the border between Nepal and India.
-
E.
Gasherbrum II
Gasherbrum II is one of the world’s fourteen eight-thousanders, a major Himalayan peak standing 8,035 meters tall on the China–Pakistan border.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a093ac988190bb339616a3ed5adb |
completed | March 1, 2026, 8:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a6374ee9ac819091abef4167e3433e |
completed | March 3, 2026, 1:20 a.m. |
Created at: March 1, 2026, 7:36 p.m.