Triple
T6172397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helion Energy |
E137733
|
entity |
| Predicate | usesEnergyConversion |
P69207
|
FINISHED |
| Object | fusion to electricity |
—
|
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: fusion to electricity | Statement: [Helion Energy, usesEnergyConversion, fusion to electricity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEnergyConversion Context triple: [Helion Energy, usesEnergyConversion, fusion to electricity]
-
A.
emitsMoreEnergyThanItReceives
Indicates that the subject releases a greater amount of energy than it takes in from its surroundings or inputs.
-
B.
energyContribution
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
-
C.
usesElectricityFor
Indicates that one entity relies on or employs electricity as the power source to operate, perform a function, or carry out an activity for another entity or purpose.
-
D.
storesEnergyAs
Indicates that one entity retains or accumulates energy in the form or medium specified by another entity.
-
E.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d9319548190980c99f692bd4115 |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.