Triple
T22215105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Line (Sri Lanka) |
E549054
|
entity |
| Predicate | maximumElevationApprox |
P19320
|
FINISHED |
| Object | over 1,800 metres above sea level |
—
|
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: over 1,800 metres above sea level | Statement: [Main Line (Sri Lanka), maximumElevationApprox, over 1,800 metres above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumElevationApprox Context triple: [Main Line (Sri Lanka), maximumElevationApprox, over 1,800 metres above sea level]
-
A.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
B.
highestElevationApprox
chosen
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
C.
peakElevationMetres
Indicates the maximum height of an entity above sea level, measured in metres.
-
D.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
E.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b8bdfbc8190832809edbe8b7c27 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.