Triple
T17446106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welshpool and Llanfair Light Railway |
E424787
|
entity |
| Predicate | closureToPassengerTraffic |
P10433
|
FINISHED |
| Object | 1931 |
—
|
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: 1931 | Statement: [Welshpool and Llanfair Light Railway, closureToPassengerTraffic, 1931]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureToPassengerTraffic Context triple: [Welshpool and Llanfair Light Railway, closureToPassengerTraffic, 1931]
-
A.
openedToPassengerTraffic
Indicates that a transportation facility or route began operating and accepting passengers for regular use.
-
B.
closedForPassengers
chosen
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
C.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
-
D.
passengerTraffic
Indicates the flow or volume of passengers moving through or using a particular transport service, route, or facility.
-
E.
servesPassengerTrafficTo
Indicates that a transportation facility or service provides regular passenger traffic access or operations to a particular location or area.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffafec48190b25980318cea353f |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.