Triple
T6971891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roof of the World |
E161616
|
entity |
| Predicate | altitudeType |
P6557
|
FINISHED |
| Object | high-altitude |
—
|
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: high-altitude | Statement: [Roof of the World, altitudeType, high-altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeType Context triple: [Roof of the World, altitudeType, high-altitude]
-
A.
altitudeCategory
Indicates the classification of something based on its height or elevation relative to a reference level (e.g., low, medium, high altitude).
-
B.
elevationType
chosen
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
C.
altitudeProfile
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
-
D.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
-
E.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db398f10819096d34b179ccb20d5 |
completed | March 27, 2026, 7:32 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.