Triple
T5453170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London St Pancras to Sheffield |
E122415
|
entity |
| Predicate | routeLengthApproxKm |
P22795
|
FINISHED |
| Object | 260 |
—
|
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: 260 | Statement: [London St Pancras to Sheffield, routeLengthApproxKm, 260]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeLengthApproxKm Context triple: [London St Pancras to Sheffield, routeLengthApproxKm, 260]
-
A.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
B.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
C.
navigableLengthApproxKm
Indicates the approximate distance, measured in kilometers, over which something (typically a waterway) can be navigated.
-
D.
approximateDistanceKm
chosen
Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
-
E.
range_km
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.