Triple
T25445169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnt Fen |
E637614
|
entity |
| Predicate | hasRailwayStationSuccessor |
P46397
|
FINISHED |
| Object | Shippea Hill railway station |
—
|
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: Shippea Hill railway station | Statement: [Burnt Fen, hasRailwayStationSuccessor, Shippea Hill railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayStationSuccessor Context triple: [Burnt Fen, hasRailwayStationSuccessor, Shippea Hill railway station]
-
A.
hasSuccessorStationName
Indicates that one station is immediately followed by another station, whose name is given as the successor station name.
-
B.
successorStation
chosen
Indicates that one station directly follows another in a sequence, such as along a transit line or route.
-
C.
hasCitySuccessor
Indicates that one city is the successor or replacement of another city, typically in terms of status, function, or administrative role.
-
D.
precedingStation
Indicates that one station is located immediately before another station in a route or sequence.
-
E.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 2 p.m.