Triple
T36763903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upminster station |
E908281
|
entity |
| Predicate | hasAdjacentStationOnNationalRail |
P163020
|
FINISHED |
| Object | West Horndon |
—
|
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: West Horndon | Statement: [Upminster station, hasAdjacentStationOnNationalRail, West Horndon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentStationOnNationalRail Context triple: [Upminster station, hasAdjacentStationOnNationalRail, West Horndon]
-
A.
hasAdjacentNationalRailStation
chosen
Indicates that one location has a national rail station situated directly next to or immediately beside it.
-
B.
hasAdjacentStationTowardsCentralLondon
Indicates that one station has a neighboring station located in the direction of central London along a transit route.
-
C.
hasAdjacentStationOnElizabethLine
Indicates that one station is directly next to another station along the Elizabeth Line, with no other stations in between.
-
D.
hasAdjacentStationOnCentralLine
Indicates that one station is directly next to another station along the Central Line.
-
E.
adjacentToStation
Indicates that one entity is located next to or immediately beside a station.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.