Triple

T34984245
Position Surface form Disambiguated ID Type / Status
Subject H-bomb E1008897 entity
Predicate usesPhysicalProcess P191039 FINISHED
Object nuclear fusion 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: nuclear fusion | Statement: [H-bomb, usesPhysicalProcess, nuclear fusion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesPhysicalProcess
Context triple: [H-bomb, usesPhysicalProcess, nuclear fusion]
  • A. hasPhysicalNature
    Indicates that one entity possesses or exhibits a specific physical form, composition, or material nature in relation to another.
  • B. supportsPhysics
    Indicates that one entity provides the necessary capabilities or features for another entity to handle, simulate, or work with physical behaviors or physics-based interactions.
  • C. operatesOnPhysicalSystem
    Indicates that an agent or process performs actions that affect or manipulate a physical system.
  • D. isPhysicalArtifact
    Indicates that the subject is a tangible, man-made object that physically exists in the real world.
  • E. physicalRequirement
    Indicates that one entity specifies a necessary physical condition, capability, or resource that must be met or possessed for another entity, action, or process to occur or be valid.
  • 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_69f76dc844a48190881951fffb83d17e completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcd867f36081908c88c55a6a1404c1 completed May 7, 2026, 6:22 p.m.
PD Predicate disambiguation batch_69fcd1f47b188190b4cf4b4c748d9d03 completed May 7, 2026, 5:55 p.m.
PDg Predicate description generation batch_69fcd866dd248190bff61c43bee93f54 completed May 7, 2026, 6:22 p.m.
Created at: May 3, 2026, 4:01 p.m.