Triple
T24880617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Tynedale Railway |
E622695
|
entity |
| Predicate | extensionToSlaggyfordOpened |
P158131
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [South Tynedale Railway, extensionToSlaggyfordOpened, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensionToSlaggyfordOpened Context triple: [South Tynedale Railway, extensionToSlaggyfordOpened, 2017]
-
A.
openedLondonExtension
Indicates that an entity initiated and made available a new extension or branch located in London.
-
B.
extensionToHudsonYardsOpened
Indicates that a transit line or service extension leading to Hudson Yards has been officially opened for operation.
-
C.
extendedFor
Indicates that something has been lengthened in duration, scope, or extent specifically for the benefit or use of another entity.
-
D.
extensionOpeningPeriod
Indicates the time span during which an extension (such as a facility, service, or feature) is open or available for use.
-
E.
southernExtensionOpeningDate
Indicates the date on which the southern extension of something (such as a route, line, or facility) was officially opened or began operation.
- F. None of above. chosen
Provenance (4 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 5:24 a.m.