Triple
T18890668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadmoor Manitou and Pikes Peak Cog Railway |
E462076
|
entity |
| Predicate | previousPowerType |
P133699
|
FINISHED |
| Object | steam |
—
|
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: steam | Statement: [Broadmoor Manitou and Pikes Peak Cog Railway, previousPowerType, steam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPowerType Context triple: [Broadmoor Manitou and Pikes Peak Cog Railway, previousPowerType, steam]
-
A.
powersType
Indicates that one entity has a specific type or category of power or ability in relation to another entity.
-
B.
hadPowerType
Indicates that an entity possessed or was associated with a specific type or category of power.
-
C.
laterPowerOutput
Indicates that the power output of an entity at a later time is being related or compared to its power output at an earlier time.
-
D.
typicalPower
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
-
E.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69e4afa745c081908da20a51ebc147b4 |
completed | April 19, 2026, 10:34 a.m. |
Created at: April 10, 2026, 11:58 a.m.