Triple
T10815778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kongur Tagh |
E255223
|
entity |
| Predicate | globalElevationRank |
P39147
|
FINISHED |
| Object | one of the highest mountains 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: one of the highest mountains in the world | Statement: [Kongur Tagh, globalElevationRank, one of the highest mountains in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalElevationRank Context triple: [Kongur Tagh, globalElevationRank, one of the highest mountains in the world]
-
A.
regionRankByHeight
Indicates the relative ordering of regions based on their height or elevation.
-
B.
summitElevationRank
chosen
Indicates the relative position of a summit in an ordered list based on its elevation compared to other summits.
-
C.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
D.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
E.
post-elevationRank
Indicates that one entity holds a higher or later elevation-based rank or status than another entity.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733edab248190b2cf7f7bc2684468 |
completed | April 9, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.