Triple

T23908792
Position Surface form Disambiguated ID Type / Status
Subject ITER project E601277 entity
Predicate designedEnergyGainFactor P130550 FINISHED
Object Q ≥ 10 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: Q ≥ 10 | Statement: [ITER project, designedEnergyGainFactor, Q ≥ 10]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedEnergyGainFactor
Context triple: [ITER project, designedEnergyGainFactor, Q ≥ 10]
  • A. designEnergy
    Indicates that an entity is responsible for planning, specifying, or determining the energy-related characteristics or performance of another entity.
  • B. designedFusionGainQ chosen
    Indicates that something has a specified or intended fusion energy gain (output-to-input energy ratio) by design.
  • C. designedCenterOfMassEnergy
    Indicates that one entity specifies the intended or planned center-of-mass energy at which another entity (such as an experiment, collider, or process) is meant to operate.
  • D. energyContribution
    Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
  • E. energyDependence
    Indicates that one entity’s state, behavior, or outcome is contingent on or influenced by the amount, source, or availability of energy associated with 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_69e295364a488190bcac702e9bb7f764 completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1ce92e7688190ac421570e0d6a942 completed April 29, 2026, 9:25 a.m.
PD Predicate disambiguation batch_69f16151ebdc819086e9e1d7cc1f4f3c completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:37 p.m.