Triple
T24880615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Tynedale Railway |
E622695
|
entity |
| Predicate | trackReopenedInStagesFrom |
P26029
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [South Tynedale Railway, trackReopenedInStagesFrom, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackReopenedInStagesFrom Context triple: [South Tynedale Railway, trackReopenedInStagesFrom, 1983]
-
A.
reopenedHistoricRoute
Indicates that a previously closed or inactive historic route has been opened again for use or access.
-
B.
openedInStages
chosen
Indicates that the opening or launch of something occurred in multiple distinct phases or stages rather than all at once.
-
C.
reopenedBy
Indicates that a previously closed or resolved item, case, or process has been opened again by a specific agent or entity.
-
D.
reopenedAfter
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
E.
reopenedAsPartOf
Indicates that an entity was reopened as a component or phase within a larger, ongoing process, case, or 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:24 a.m.