Triple
T23088034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egton railway station |
E575665
|
entity |
| Predicate | distanceFromMiddlesbroughByRail |
P86998
|
FINISHED |
| Object | approximately 32 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 32 miles | Statement: [Egton railway station, distanceFromMiddlesbroughByRail, approximately 32 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMiddlesbroughByRail Context triple: [Egton railway station, distanceFromMiddlesbroughByRail, approximately 32 miles]
-
A.
distanceFromMiddlesbrough
chosen
Indicates the spatial distance between an entity’s location and the town of Middlesbrough.
-
B.
distanceFromBanburyByRail
Indicates the distance between a place and Banbury when traveling by railway.
-
C.
distanceToScunthorpe
Indicates the measured or calculated distance between a given entity’s location and the town of Scunthorpe.
-
D.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
-
E.
distanceToBurnley
Indicates the measured spatial distance between a given entity and the location Burnley.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da7c54c81908b62d04ab1811b06 |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.