Triple
T37233262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G1 |
E923197
|
entity |
| Predicate | hasHeightAboveSeaLevel |
P114161
|
FINISHED |
| Object | 8080 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: 8080 m | Statement: [G1, hasHeightAboveSeaLevel, 8080 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeightAboveSeaLevel Context triple: [G1, hasHeightAboveSeaLevel, 8080 m]
-
A.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
-
B.
hasElevationRelativeToSeaLevel
chosen
Indicates the elevation or height of an entity measured relative to mean sea level.
-
C.
emergedAboveSeaLevel
Indicates that something rose or became exposed above the surface of the sea from a previously submerged or lower position.
-
D.
elevationAboveSurroundingPlains
Indicates that something is situated at a higher altitude than the nearby flat or low-lying surrounding plains.
-
E.
countryAltitudeCharacteristic
Indicates a characteristic relationship specifying the typical or notable altitude or elevation associated with a country.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 3, 2026, 4:15 p.m.