Triple
T9645987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Albans Abbey railway station |
E233195
|
entity |
| Predicate | distanceFromWatfordJunction |
P89419
|
FINISHED |
| Object | approximately 6.5 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 6.5 miles | Statement: [St Albans Abbey railway station, distanceFromWatfordJunction, approximately 6.5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromWatfordJunction Context triple: [St Albans Abbey railway station, distanceFromWatfordJunction, approximately 6.5 miles]
-
A.
distanceToHertford
Indicates the spatial distance between a given entity and the location of Hertford.
-
B.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
C.
distanceToTelford
Indicates the spatial distance between a given entity and the location of Telford.
-
D.
distanceFromMiltonKeynes
Indicates the measured spatial distance between a given entity’s location and the location of Milton Keynes.
-
E.
distanceToStevenage
Indicates the spatial distance between a given entity or location and Stevenage.
- F. None of above. chosen
Provenance (4 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b8122148190bd0af3a04b21e53e |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:12 p.m.