Triple
T8309753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khumbu |
E194560
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Kongde Ri |
E187804
|
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: Kongde Ri | Statement: [Khumbu, contains, Kongde Ri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kongde Ri Context triple: [Khumbu, contains, Kongde Ri]
-
A.
Kongde Ri
chosen
Kongde Ri is a prominent Himalayan peak in Nepal known for its striking multi-summited massif overlooking the Everest region.
-
B.
Kangchungtse
Kangchungtse is a high Himalayan subpeak of Mount Makalu located on the Nepal–Tibet border.
-
C.
Koung-Khi
Koung-Khi is an administrative department located in the West Region of Cameroon.
-
D.
Sungsang
Sungsang is a coastal village in South Sumatra, Indonesia, known as a fishing and port settlement near the mouth of the Musi River.
-
E.
Chang La
Chang La is a high-altitude mountain pass in the Indian Himalayas, known as one of the world’s highest motorable roads and a key route toward the Pangong Lake region in Ladakh.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2d2c30819095075940479b75a7 |
completed | March 31, 2026, 8 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd95665390819089c8becad018cf51 |
completed | April 1, 2026, 10 p.m. |
Created at: March 30, 2026, 5:54 p.m.