Triple

T31032247
Position Surface form Disambiguated ID Type / Status
Subject Unit 4 reactor building E790757 entity
Predicate seismicReinforcement P13028 FINISHED
Object installed after 2011 accident 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: installed after 2011 accident | Statement: [Unit 4 reactor building, seismicReinforcement, installed after 2011 accident]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: seismicReinforcement
Context triple: [Unit 4 reactor building, seismicReinforcement, installed after 2011 accident]
  • A. seismicRetrofit chosen
    Indicates that an existing structure has been modified or strengthened to improve its performance and safety during seismic events such as earthquakes.
  • B. seismicDesign
    Indicates that an entity is designed or engineered to withstand seismic activity or earthquake-related forces.
  • C. earthquakeResistance
    Indicates how well an entity can withstand or remain functional during an earthquake without significant damage.
  • D. seismicSafetyConcernsIdentified
    Indicates that potential risks or issues related to seismic safety have been detected or recognized.
  • E. hasSeismicBehavior
    Indicates that an entity exhibits or is characterized by a particular type or pattern of seismic activity or response.
  • 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_69f224c97a788190b5da1ead6038a74e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f694c2fe008190b643a2b2d8274669 completed May 3, 2026, 12:20 a.m.
PD Predicate disambiguation batch_69f690f13d7481908ddfefe95df2a1c2 completed May 3, 2026, 12:04 a.m.
Created at: April 29, 2026, 8:59 p.m.