Triple
T29847154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodmansterne railway station |
E757959
|
entity |
| Predicate | toCentralLondonVia |
P167662
|
FINISHED |
| Object | East Croydon |
—
|
NE NERFINISHED |
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 Croydon | Statement: [Woodmansterne railway station, toCentralLondonVia, East Croydon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toCentralLondonVia Context triple: [Woodmansterne railway station, toCentralLondonVia, East Croydon]
-
A.
servesCentralLondon
Indicates that something provides service or access specifically to the Central London area.
-
B.
timeToCentralLondonByTrain
Indicates the amount of time it takes to travel by train from a given location to central London.
-
C.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
D.
hasTerminusInCentralLondon
Indicates that the route, service, or line ends at a terminal point located within Central London.
-
E.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
- 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_69f6764489c881909618ff635fe6c410 |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66bd123108190b451eb6e23842adb |
completed | May 2, 2026, 9:25 p.m. |
Created at: April 29, 2026, 5:42 p.m.