Triple
T2483175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltoro Glacier |
E55865
|
entity |
| Predicate | terminusElevation |
P221
|
FINISHED |
| Object | about 3450 m |
—
|
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: about 3450 m | Statement: [Baltoro Glacier, terminusElevation, about 3450 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusElevation Context triple: [Baltoro Glacier, terminusElevation, about 3450 m]
-
A.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
B.
elevationFrom
Indicates a vertical distance relationship where one entity’s height or altitude is measured relative to another reference entity.
-
C.
elevationAtBase
Indicates the height or altitude measured at the base or lowest point of an object or feature relative to a reference level.
-
D.
elevation
chosen
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
E.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.