Triple
T6690230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chertsey railway station |
E152604
|
entity |
| Predicate | hasDistanceFromLondonWaterloo |
P8256
|
FINISHED |
| Object | 21 miles 40 chains |
—
|
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: 21 miles 40 chains | Statement: [Chertsey railway station, hasDistanceFromLondonWaterloo, 21 miles 40 chains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistanceFromLondonWaterloo Context triple: [Chertsey railway station, hasDistanceFromLondonWaterloo, 21 miles 40 chains]
-
A.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
B.
distanceToLondon
chosen
Indicates the measured distance between a given entity’s location and the city of London.
-
C.
distanceToGatwickAirport
Indicates the measured distance between a given entity’s location and Gatwick Airport.
-
D.
distanceToYorkCityCentre
Indicates the measured or specified distance between a given location and the centre of York city.
-
E.
distanceToEgham
Indicates the spatial distance between a given entity and the location of Egham.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:04 p.m.