Triple

T31016309
Position Surface form Disambiguated ID Type / Status
Subject Fukushima Daini Nuclear Power Plant E790334 entity
Predicate designedForSeismicSafety P8962 FINISHED
Object yes 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: yes | Statement: [Fukushima Daini Nuclear Power Plant, designedForSeismicSafety, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedForSeismicSafety
Context triple: [Fukushima Daini Nuclear Power Plant, designedForSeismicSafety, yes]
  • A. seismicDesign chosen
    Indicates that an entity is designed or engineered to withstand seismic activity or earthquake-related forces.
  • B. earthquakeResistance
    Indicates how well an entity can withstand or remain functional during an earthquake without significant damage.
  • C. seismicDesignCategory
    Indicates the classification of a structure’s required level of seismic resistance based on its expected exposure to earthquake forces.
  • D. hasSeismicBehavior
    Indicates that an entity exhibits or is characterized by a particular type or pattern of seismic activity or response.
  • E. seismicRetrofit
    Indicates that an existing structure has been modified or strengthened to improve its performance and safety during seismic events such as earthquakes.
  • 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_69f224c811508190a7de096a5b1f5798 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fd7fdafbe881908a31fcb407af2c34 completed May 8, 2026, 6:16 a.m.
PD Predicate disambiguation batch_69fd7ef0ea908190b5d83f71565bdb1c completed May 8, 2026, 6:13 a.m.
Created at: April 29, 2026, 8:57 p.m.