Triple
T36632716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Lynn |
E904369
|
entity |
| Predicate | wasRailwayHubOn |
P170780
|
FINISHED |
| Object | Midland and Great Northern Joint Railway |
—
|
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: Midland and Great Northern Joint Railway | Statement: [South Lynn, wasRailwayHubOn, Midland and Great Northern Joint Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRailwayHubOn Context triple: [South Lynn, wasRailwayHubOn, Midland and Great Northern Joint Railway]
-
A.
hadRailwayStation
Indicates that a place or area previously possessed a railway station, which may no longer be in existence or operation.
-
B.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
C.
isRegionalRailwayHub
chosen
Indicates that a location functions as a central node in a regional railway network, where multiple rail lines converge or are coordinated.
-
D.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
E.
isRailHubFor
Indicates that a location functions as a central node or interchange point within a rail network for the referenced area, routes, or services.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.