Triple
T30082127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apsley railway station |
E764498
|
entity |
| Predicate | formerRailwayRegion |
P147854
|
FINISHED |
| Object | London Midland Region |
—
|
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: London Midland Region | Statement: [Apsley railway station, formerRailwayRegion, London Midland Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerRailwayRegion Context triple: [Apsley railway station, formerRailwayRegion, London Midland Region]
-
A.
railwayRegion
Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
-
B.
formerRailwayZone
chosen
Indicates that an entity was previously part of a specified railway administrative zone or system, but is no longer within that zone.
-
C.
formerRailwayLine
Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
-
D.
formerRailroadCorridor
Indicates that a location or route once served as a railroad corridor but is no longer used for active rail service.
-
E.
formerRailroad
Indicates that an entity was previously a railroad but no longer functions as one.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: April 29, 2026, 7:03 p.m.