Triple
T16443784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatch Unit 2 |
E399372
|
entity |
| Predicate | thermalToElectricConversion |
P95815
|
FINISHED |
| Object | steam turbine |
—
|
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 turbine | Statement: [Hatch Unit 2, thermalToElectricConversion, steam turbine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermalToElectricConversion Context triple: [Hatch Unit 2, thermalToElectricConversion, steam turbine]
-
A.
usesEnergyConversion
Indicates that an entity performs or involves a process where one form of energy is transformed into another to achieve a function or outcome.
-
B.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
C.
emitsMoreEnergyThanItReceives
Indicates that the subject releases a greater amount of energy than it takes in from its surroundings or inputs.
-
D.
energyGenerationMechanism
chosen
Indicates the method or process by which energy is produced or generated by an entity.
-
E.
powerConversionSystem
Indicates a system that transforms electrical power from one form, level, or source into another to meet specific usage or distribution requirements.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cd9d474819091b4a80de1019c54 |
completed | April 18, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.