Triple
T31867782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alstom |
E813505
|
entity |
| Predicate | saleOfEnergyBusinessCompletion |
P155262
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Alstom, saleOfEnergyBusinessCompletion, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saleOfEnergyBusinessCompletion Context triple: [Alstom, saleOfEnergyBusinessCompletion, 2015]
-
A.
energyExporter
Indicates that an entity supplies or sells energy resources or power to other entities, typically across regional or national boundaries.
-
B.
electrificationCompleted
Indicates that the process of providing electrical power infrastructure to the relevant entity or area has been fully completed.
-
C.
electricityMarket
Indicates a relationship where entities participate in, are associated with, or operate within a system for buying, selling, or trading electrical power.
-
D.
saleResultedIn
chosen
Indicates that a particular sale transaction led to or caused a specific outcome, consequence, or resulting state.
-
E.
energySystemOperator
Indicates that one entity operates, manages, or controls an energy system on behalf of or in relation to another entity.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b094d7b881908c82c8a54665d20f |
completed | May 3, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:54 p.m.