Triple

T9709465
Position Surface form Disambiguated ID Type / Status
Subject Fukushima Daiichi Unit 4 E234984 entity
Predicate hydrogenExplosionSource P90379 FINISHED
Object hydrogen from Unit 3 via shared venting or piping 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: hydrogen from Unit 3 via shared venting or piping | Statement: [Fukushima Daiichi Unit 4, hydrogenExplosionSource, hydrogen from Unit 3 via shared venting or piping]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hydrogenExplosionSource
Context triple: [Fukushima Daiichi Unit 4, hydrogenExplosionSource, hydrogen from Unit 3 via shared venting or piping]
  • A. hydrogenExplosionsOccurredIn
    Indicates that one or more hydrogen explosions took place at the specified location or within the specified context.
  • B. hydrogenExplosionDate
    Indicates the date on which a hydrogen explosion occurred or is scheduled to occur.
  • C. consequenceOfExplosion
    Indicates that something occurs as a direct result or outcome of an explosion.
  • D. explosionAltitude
    Indicates the height above a reference surface at which an explosion occurs or is triggered.
  • E. explosiveMaterialUsed
    Indicates that an explosive material was employed or involved in carrying out a particular action or event.
  • 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_69ca84cd8fa0819090a5e243ceb37003 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9da7c6188190b086f7e411378268 completed April 1, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69cd03bfeca08190924fca43aaa9c10f completed April 1, 2026, 11:38 a.m.
PDg Predicate description generation batch_69cd06aa8bc88190904be19c8953def8 completed April 1, 2026, 11:51 a.m.
Created at: March 30, 2026, 8:19 p.m.