Triple
T31016524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大熊町 |
E790338
|
entity |
| Predicate | evacuationOrderIssued |
P87487
|
FINISHED |
| Object | 2011-03-2011-04（原発事故に伴う避難指示） |
—
|
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: 2011-03-2011-04（原発事故に伴う避難指示） | Statement: [大熊町, evacuationOrderIssued, 2011-03-2011-04（原発事故に伴う避難指示）]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuationOrderIssued Context triple: [大熊町, evacuationOrderIssued, 2011-03-2011-04（原発事故に伴う避難指示）]
-
A.
evacuationOrderIssuedBy
Indicates that a specific authority or organization has formally issued an evacuation order for people to leave a particular area.
-
B.
evacuationOrderedIn
chosen
Indicates that an official evacuation has been ordered to occur within a specified location or area.
-
C.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
D.
evacuationReason
Indicates the cause or justification for why an evacuation took place or was required.
-
E.
evacuationPoint
Indicates a location designated as the place where people should gather or be moved to during an evacuation.
- 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_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:57 p.m.