Triple
T13398103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikkim Himalaya |
E319753
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Kangchenjunga |
E33414
|
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: Kangchenjunga | Statement: [Sikkim Himalaya, contains, Kangchenjunga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kangchenjunga Context triple: [Sikkim Himalaya, contains, Kangchenjunga]
-
A.
Kangchenjunga
chosen
Kangchenjunga is the world’s third-highest mountain, a massive peak in the eastern Himalayas on the border between Nepal and India.
-
B.
Makalu
Makalu is the fifth-highest mountain in the world, a prominent 8,485-meter peak on the border between Nepal and China known for its steep faces and challenging climbing routes.
-
C.
Shishapangma
Shishapangma is one of the world’s fourteen eight-thousanders, a major Himalayan peak located entirely within Tibet, China.
-
D.
Himalchuli
Himalchuli is a prominent high-altitude mountain peak in the Nepalese Himalayas, known as one of the major summits of the Mansiri Himal range.
-
E.
Cho Oyu
Cho Oyu is the world’s sixth-highest mountain, an 8,188-meter peak in the Mahalangur Himal section of the Himalayas near the Nepal–China 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d9e7348190844e11dd6cbd13b0 |
completed | April 12, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78ad2c4dc819083d23448d21bb0f3 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:34 p.m.