Triple
T27569773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gokyo Ri |
E695999
|
entity |
| Predicate | regionAltitudeRange |
P122621
|
FINISHED |
| Object | around 4700–5400 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: around 4700–5400 m | Statement: [Gokyo Ri, regionAltitudeRange, around 4700–5400 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionAltitudeRange Context triple: [Gokyo Ri, regionAltitudeRange, around 4700–5400 m]
-
A.
tracksAltitudeRange
Indicates that something monitors or records the minimum and maximum altitude values over a given period or area.
-
B.
altitudeRange_m
chosen
Indicates the range of altitudes, measured in meters, over which the relationship or condition holds.
-
C.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
D.
altitudeRangeReported
Indicates that a specific range of altitudes has been reported for an entity or event, rather than a single altitude value.
-
E.
operationalAltitudeBand
Indicates the range of altitudes within which an entity is intended or allowed to operate.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 27, 2026, 1:43 p.m.