Triple
T28068260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalmarnock railway station |
E709315
|
entity |
| Predicate | closedForRebuilding |
P116566
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Dalmarnock railway station, closedForRebuilding, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedForRebuilding Context triple: [Dalmarnock railway station, closedForRebuilding, 2011]
-
A.
closedForReconstructionTo
chosen
Indicates that access or use of something is prohibited for a party because it is undergoing reconstruction.
-
B.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
C.
closedDuring
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
D.
closedForSafety
Indicates that an entity (such as a place, facility, or route) is temporarily unavailable or inaccessible due to safety concerns or hazards.
-
E.
closedForProduction
Indicates that an entity (such as a facility, system, or resource) is temporarily unavailable or shut down due to ongoing production activities or processes.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 8:44 p.m.