Triple
T26641506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwest Face route on Kangchenjunga |
E668791
|
entity |
| Predicate | mountainRank |
P39147
|
FINISHED |
| Object | third-highest mountain in the world |
—
|
LITERAL 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: third-highest mountain in the world | Statement: [Southwest Face route on Kangchenjunga, mountainRank, third-highest mountain in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainRank Context triple: [Southwest Face route on Kangchenjunga, mountainRank, third-highest mountain in the world]
-
A.
summitElevationRank
chosen
Indicates the relative position of a summit in an ordered list based on its elevation compared to other summits.
-
B.
endPointMountain
Indicates that a path, route, or boundary terminates at a mountain.
-
C.
mountainType
Indicates the specific classification or category of a mountain based on its geological or physical characteristics.
-
D.
FIDERankingPeak
Indicates the highest FIDE (chess) rating or ranking position an entity has ever achieved.
-
E.
mountainHeight
Indicates the vertical elevation or height of a mountain, typically measured from sea level.
- F. None of above.
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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616320b9c8190b3a5792ffcfe3bc1 |
completed | May 2, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:29 a.m.