Triple
T831788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woking railway station |
E17980
|
entity |
| Predicate | distanceFromLondonWaterloo |
P8256
|
FINISHED |
| Object | approximately 23 miles |
—
|
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: approximately 23 miles | Statement: [Woking railway station, distanceFromLondonWaterloo, approximately 23 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromLondonWaterloo Context triple: [Woking railway station, distanceFromLondonWaterloo, approximately 23 miles]
-
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.
distanceFromEdinburghWaverley
Indicates the measured distance between a given location and Edinburgh Waverley station.
-
D.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
E.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb4be948190ae757df85bdc40e4 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.