Triple
T8000076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haddenham and Thame Parkway railway station |
E186223
|
entity |
| Predicate | directionFromLondonMarylebone |
P15847
|
FINISHED |
| Object | 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: northwest | Statement: [Haddenham and Thame Parkway railway station, directionFromLondonMarylebone, northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromLondonMarylebone Context triple: [Haddenham and Thame Parkway railway station, directionFromLondonMarylebone, northwest]
-
A.
directionFromLondon
chosen
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
B.
directionFromManchesterCityCentre
Indicates the compass direction in which one location lies when measured outward from Manchester city centre.
-
C.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
D.
geographicDirectionFromEdinburgh
Indicates the geographic direction in which one place or entity is located relative to Edinburgh.
-
E.
directionFromCityCentre
Indicates the compass direction in which one location lies relative to the city centre.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c9b67988190a8a4a2c960017400 |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:17 p.m.