Triple
T13118535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Byfleet railway station |
E311661
|
entity |
| Predicate | directionFromLondonWaterloo |
P74413
|
FINISHED |
| Object | southwest |
—
|
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: southwest | Statement: [West Byfleet railway station, directionFromLondonWaterloo, southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromLondonWaterloo Context triple: [West Byfleet railway station, directionFromLondonWaterloo, southwest]
-
A.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
B.
directionFromLondonKingsCross
Indicates the direction or bearing of a location when traveling from London King's Cross.
-
C.
directionFromWaterloo
chosen
Indicates the cardinal or relative direction of one location when measured outward starting from Waterloo.
-
D.
directionFromManchesterCityCentre
Indicates the compass direction in which one location lies when measured outward from Manchester city centre.
-
E.
directionFromOxford
Indicates the cardinal or relative compass direction of one place or object as measured from Oxford.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98182011c8190a504678affbb7787 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.