Triple
T30082113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apsley railway station |
E764498
|
entity |
| Predicate | directionFromLondonEuston |
P190053
|
FINISHED |
| Object | north-west |
—
|
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-west | Statement: [Apsley railway station, directionFromLondonEuston, north-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromLondonEuston Context triple: [Apsley railway station, directionFromLondonEuston, north-west]
-
A.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
B.
directionFromLondonFenchurchStreet
Indicates the compass direction or bearing of one place or object as measured from London Fenchurch Street.
-
C.
directionFromLondonKingsCross
Indicates the direction or bearing of a location when traveling from London King's Cross.
-
D.
lineDirectionFromCentralLondon
Indicates the directional bearing or route of a line as measured outward from a central reference point in London.
-
E.
directionFromLiverpoolStreet
Indicates the directional relationship of one place or object as measured outward from 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: April 29, 2026, 7:03 p.m.