Triple
T16305722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qinghai–Tibet Railway |
E395904
|
entity |
| Predicate | highestPoint_elevation_m |
P19320
|
FINISHED |
| Object | about 5072 |
—
|
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 5072 | Statement: [Qinghai–Tibet Railway, highestPoint_elevation_m, about 5072]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestPoint_elevation_m Context triple: [Qinghai–Tibet Railway, highestPoint_elevation_m, about 5072]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
highestElevationApprox
chosen
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
C.
eastSummitElevation
Indicates the elevation of the summit located on the eastern side of a geographic feature or area.
-
D.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
-
E.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288d5619081909d0f8157cc487877 |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.