Triple
T18890672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadmoor Manitou and Pikes Peak Cog Railway |
E462076
|
entity |
| Predicate | closureForReconstruction |
P116566
|
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: [Broadmoor Manitou and Pikes Peak Cog Railway, closureForReconstruction, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureForReconstruction Context triple: [Broadmoor Manitou and Pikes Peak Cog Railway, closureForReconstruction, 2017]
-
A.
closedForReconstructionTo
chosen
Indicates that access or use of something is prohibited for a party because it is undergoing reconstruction.
-
B.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
C.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
-
D.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
E.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c47ab34c8190bfb69444a5263538 |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.