Triple
T16470393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballymena, Cushendall and Red Bay Railway |
E400043
|
entity |
| Predicate | passengerServiceClosed |
P10433
|
FINISHED |
| Object | 1940-10-01 |
—
|
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: 1940-10-01 | Statement: [Ballymena, Cushendall and Red Bay Railway, passengerServiceClosed, 1940-10-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerServiceClosed Context triple: [Ballymena, Cushendall and Red Bay Railway, passengerServiceClosed, 1940-10-01]
-
A.
closedForPassengers
chosen
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
B.
openedAsPassengerService
Indicates that a transportation facility or route began operating specifically for carrying passengers.
-
C.
railServiceEnded
Indicates that a previously operating rail service has been discontinued or terminated.
-
D.
formerPassengerService
Indicates that an entity previously provided passenger transportation services but no longer does so.
-
E.
airportPassengerServiceEndedAt
Indicates that the provision of passenger-related services at an airport concluded at a specific time or event.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dd0d2fc81909b68b5afb00f192f |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.