Triple
T29848376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilford railway station |
E757994
|
entity |
| Predicate | directionFromLiverpoolStreet |
P188431
|
FINISHED |
| Object | north-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: north-east | Statement: [Ilford railway station, directionFromLiverpoolStreet, north-east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromLiverpoolStreet Context triple: [Ilford railway station, directionFromLiverpoolStreet, north-east]
-
A.
directionFromLondonFenchurchStreet
Indicates the compass direction or bearing of one place or object as measured from London Fenchurch Street.
-
B.
distanceFromLiverpoolStreet
Indicates the measured distance between a given location and Liverpool Street.
-
C.
directionFromLondonKingsCross
Indicates the direction or bearing of a location when traveling from London King's Cross.
-
D.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
E.
adjacentStationTowardsLiverpoolStreet
Indicates that one station is directly next to another along the route in the direction of Liverpool Street.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: April 29, 2026, 5:42 p.m.