Triple
T4625337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stratford-upon-Avon railway station |
E101083
|
entity |
| Predicate | distanceFromBirminghamMoorStreet |
P13288
|
FINISHED |
| Object | approximately 26 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 26 miles | Statement: [Stratford-upon-Avon railway station, distanceFromBirminghamMoorStreet, approximately 26 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBirminghamMoorStreet Context triple: [Stratford-upon-Avon railway station, distanceFromBirminghamMoorStreet, approximately 26 miles]
-
A.
distanceToBirmingham
chosen
Indicates the spatial distance between a given entity’s location and the city of Birmingham.
-
B.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
-
C.
distanceToSalford
Indicates the spatial distance between a given entity and the location of Salford.
-
D.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
E.
distanceFromBolton
Indicates the spatial distance between a given entity or location and the place named Bolton.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a08ef488190af46418229309b0f |
completed | March 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.