Triple
T24796089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deptford railway station |
E620385
|
entity |
| Predicate | directionFromLondonBridge |
P15847
|
FINISHED |
| Object | east |
—
|
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: east | Statement: [Deptford railway station, directionFromLondonBridge, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromLondonBridge Context triple: [Deptford railway station, directionFromLondonBridge, east]
-
A.
directionFromLondon
chosen
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
B.
directionFromBlackfriarsBridge
Indicates the directional relationship of one location or object as measured starting from Blackfriars Bridge.
-
C.
directionFromLondonKingsCross
Indicates the direction or bearing of a location when traveling from London King's Cross.
-
D.
directionFromManchesterCityCentre
Indicates the compass direction in which one location lies when measured outward from Manchester city centre.
-
E.
adjacentStationTowardsLondonBridge
Indicates that one station is directly next to another along the rail line in the direction heading toward London Bridge.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f411069830819089baad5abc40d188 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:48 a.m.