Triple

T9296226
Position Surface form Disambiguated ID Type / Status
Subject Fukushima Daiichi Nuclear Power Plant E223644 entity
Predicate evacuationZoneRadius_km P87483 FINISHED
Object 20 — 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: 20 | Statement: [Fukushima Daiichi Nuclear Power Plant, evacuationZoneRadius_km, 20]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: evacuationZoneRadius_km
Context triple: [Fukushima Daiichi Nuclear Power Plant, evacuationZoneRadius_km, 20]
  • A. evacuationRadiusInitial
    Indicates the initial distance from a source or hazard within which people or objects must be evacuated.
  • B. hasEvacuationZone
    Indicates that a specified area or location falls within a designated evacuation zone associated with another entity (such as an event, hazard, or authority).
  • C. evacuationPoint
    Indicates a location designated as the place where people should gather or be moved to during an evacuation.
  • D. hasEmergencyPlanningZone
    Indicates that an entity is associated with a designated emergency planning zone within which specific preparedness and response measures apply.
  • E. radiusOfSevereDestruction
    Indicates the distance from a central point within which damage or destruction is expected to be extremely severe.
  • 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_69ca8423edb08190bc0c91287a484768 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd089c9c588190967404c9eb938dfb completed April 1, 2026, 11:59 a.m.
PD Predicate disambiguation batch_69cc7a5aeb748190afb89c6bbd2a6d6f completed April 1, 2026, 1:52 a.m.
PDg Predicate description generation batch_69cc94b796788190816b71b1e9996288 completed April 1, 2026, 3:44 a.m.
Created at: March 30, 2026, 7:36 p.m.