Triple

T6172411
Position Surface form Disambiguated ID Type / Status
Subject Helion Energy E137733 entity
Predicate longTermVision P5437 FINISHED
Object global deployment of fusion power 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: global deployment of fusion power | Statement: [Helion Energy, longTermVision, global deployment of fusion power]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: longTermVision
Context triple: [Helion Energy, longTermVision, global deployment of fusion power]
  • A. goalHorizon
    Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
  • B. hasVisionOf
    Indicates that one entity perceives, imagines, or foresees another entity or scenario, typically in a mental, prophetic, or visualized form.
  • C. visionOf
    Indicates that one entity is a visual representation, image, or depiction of another entity.
  • D. investmentHorizon
    Indicates the typical time period over which an investment is expected to be held before its goals are evaluated or the capital is withdrawn.
  • E. strategicGoal chosen
    Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
  • 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_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.
Created at: March 22, 2026, 4:18 p.m.