Triple
T30089354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aylesbury Vale Parkway railway station |
E764683
|
entity |
| Predicate | distanceFromAylesburyStation |
P105224
|
FINISHED |
| Object | approximately 4 km northwest |
—
|
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 4 km northwest | Statement: [Aylesbury Vale Parkway railway station, distanceFromAylesburyStation, approximately 4 km northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAylesburyStation Context triple: [Aylesbury Vale Parkway railway station, distanceFromAylesburyStation, approximately 4 km northwest]
-
A.
distanceToAylesbury
chosen
Indicates the spatial distance between a given entity and the location of Aylesbury.
-
B.
distanceToHemelHempstead
Indicates the spatial distance between a given entity and the location of Hemel Hempstead.
-
C.
distanceToStAlbans
Indicates the measured distance between a given entity’s location and the location of St Albans.
-
D.
distanceFromBanburyByRail
Indicates the distance between a place and Banbury when traveling by railway.
-
E.
distanceFromWellingborough
Indicates the spatial distance measured from the reference location Wellingborough to another place or entity.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00ccadb6908190ab810a7c05315fa8 |
completed | May 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_6a00cc0f86b88190a0d2c43618558f86 |
completed | May 10, 2026, 6:18 p.m. |
Created at: April 29, 2026, 7:05 p.m.