Triple
T1979354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daiichi nuclear disaster |
E42988
|
entity |
| Predicate | expandedEvacuationZone |
P1586
|
FINISHED |
| Object | up to 30 km |
—
|
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: up to 30 km | Statement: [Fukushima Daiichi nuclear disaster, expandedEvacuationZone, up to 30 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedEvacuationZone Context triple: [Fukushima Daiichi nuclear disaster, expandedEvacuationZone, up to 30 km]
-
A.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
-
B.
notableEvacuation
Indicates a significant, widely recognized instance of people being moved or fleeing from a place for safety, typically due to danger or emergency conditions.
-
C.
majorResettlementArea
Indicates that a location serves as a primary or significant destination area where people are being resettled.
-
D.
affectedArea
chosen
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
E.
expandedTerritoryTo
Indicates that one entity has increased the geographic area under its control or influence to include the territory of another entity.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:36 p.m.