Triple
T16314658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IGN Top25 |
E396142
|
entity |
| Predicate | typicalContourInterval |
P86534
|
FINISHED |
| Object | 10 metres |
—
|
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: 10 metres | Statement: [IGN Top25, typicalContourInterval, 10 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalContourInterval Context triple: [IGN Top25, typicalContourInterval, 10 metres]
-
A.
hasContourInterval
chosen
Indicates that one entity specifies the vertical distance between contour lines represented by another entity.
-
B.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
C.
hasContourLines
Indicates that an entity (such as a map or geographic representation) includes contour lines depicting elevation or terrain shape.
-
D.
typicalHorizontalAccuracy
Indicates the usual or expected degree of precision in the horizontal (x–y) position of a measurement or location estimate.
-
E.
typicalStartElevation
Indicates the usual or characteristic elevation at which something (such as a route, feature, or activity) typically begins.
- 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_69e288de57cc81908cec93309347c385 |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.