Triple
T417429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardier M5000 |
E8024
|
entity |
| Predicate | powerSupplySystem |
P8164
|
FINISHED |
| Object | 750 V DC overhead |
—
|
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: 750 V DC overhead | Statement: [Bombardier M5000, powerSupplySystem, 750 V DC overhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSupplySystem Context triple: [Bombardier M5000, powerSupplySystem, 750 V DC overhead]
-
A.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
B.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
C.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
D.
mainCentralPower
Indicates that an entity functions as the primary central authority or dominant power within a given system or context.
-
E.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd1ca148190a66bd8c5aad867d5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.