Triple
T16918481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dungeon Hills |
E410380
|
entity |
| Predicate | elevationOfHighestPoint_metres |
P99098
|
FINISHED |
| Object | 620 |
—
|
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: 620 | Statement: [Dungeon Hills, elevationOfHighestPoint_metres, 620]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationOfHighestPoint_metres Context triple: [Dungeon Hills, elevationOfHighestPoint_metres, 620]
-
A.
peakElevationMetres
chosen
Indicates the maximum height of an entity above sea level, measured in metres.
-
B.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
-
C.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined 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.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdec3d0c8190994a0fca335c65d6 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.