Triple
T21490924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent and East Sussex Railway |
E530232
|
entity |
| Predicate | closureToFreight |
P37969
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Kent and East Sussex Railway, closureToFreight, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureToFreight Context triple: [Kent and East Sussex Railway, closureToFreight, 1961]
-
A.
lineClosedToFreight
chosen
Indicates that a railway line is not available for freight services or freight train operations.
-
B.
closedToGoods
Indicates that an entity (such as a route, border, or facility) is not open or available for the movement, trade, or handling of goods.
-
C.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
D.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
E.
freightType
Indicates the category or mode of freight associated with a shipment or transport activity.
- 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.