Triple
T21490923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent and East Sussex Railway |
E530232
|
entity |
| Predicate | closureToPassengers |
P10433
|
FINISHED |
| Object | 1954-01-02 |
—
|
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: 1954-01-02 | Statement: [Kent and East Sussex Railway, closureToPassengers, 1954-01-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureToPassengers Context triple: [Kent and East Sussex Railway, closureToPassengers, 1954-01-02]
-
A.
closedForPassengers
chosen
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
B.
passengerAccess
Indicates that a passenger is allowed to enter, use, or move through a particular vehicle, area, or transportation-related facility.
-
C.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
D.
openedAsPassengerService
Indicates that a transportation facility or route began operating specifically for carrying passengers.
-
E.
passengersSubsequentAction
Indicates the action or event that occurs to or is taken by the passengers after a preceding condition, event, or step in a process.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea3aee648190ba845f0c7d8110dd |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.