Triple
T4804438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Yorkshire Moors Railway |
E106913
|
entity |
| Predicate | closedToRegularPassengerServices |
P10433
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [North Yorkshire Moors Railway, closedToRegularPassengerServices, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedToRegularPassengerServices Context triple: [North Yorkshire Moors Railway, closedToRegularPassengerServices, 1965]
-
A.
closedForPassengers
chosen
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
B.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
C.
closureOfMostInnerCityTrams
Indicates that the most centrally located inner-city tram lines or services have been shut down or discontinued.
-
D.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
-
E.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.