Triple
T3242608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkby |
E67995
|
entity |
| Predicate | hasRailwayTerminusFunction |
P26272
|
FINISHED |
| Object | Liverpool to Kirkby line |
—
|
LITERAL FINISHED |
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: Liverpool to Kirkby line | Statement: [Kirkby, hasRailwayTerminusFunction, Liverpool to Kirkby line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayTerminusFunction Context triple: [Kirkby, hasRailwayTerminusFunction, Liverpool to Kirkby line]
-
A.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
B.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
C.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
D.
hasPassengerTerminalFunction
Indicates that something serves the role or performs the function of a passenger terminal, supporting the handling and movement of passengers.
-
E.
railLineTerminus
chosen
Indicates that a rail line ends or terminates at the specified location or 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf17463481909447f6ab46016407 |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.