Triple
T2875134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gasherbrum IV |
E56859
|
entity |
| Predicate | rankByHeightInWorld |
P2472
|
FINISHED |
| Object | 17 |
—
|
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: 17 | Statement: [Gasherbrum IV, rankByHeightInWorld, 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankByHeightInWorld Context triple: [Gasherbrum IV, rankByHeightInWorld, 17]
-
A.
rankByHeightWorld
chosen
Indicates an ordering of entities based on their relative height compared to all others in the world.
-
B.
rankAmongTallestBuildings
Indicates that one building is among the tallest buildings within a specified group, area, or category.
-
C.
rankByLengthInWorld
Indicates ordering entities within a given world or context based on their length, from shortest to longest or vice versa.
-
D.
rankInCityByHeight
Indicates the relative ordering of entities within a specific city based on their height, such as which is tallest, second tallest, and so on.
-
E.
summitElevationRank
Indicates the relative position of a summit in an ordered list based on its elevation compared to other summits.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe004a64481908f1897d9054a7368 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.