Triple
T31016628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Futaba District |
E790340
|
entity |
| Predicate | hasEvacuationZones |
P46021
|
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: [Futaba District, hasEvacuationZones, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvacuationZones Context triple: [Futaba District, hasEvacuationZones, yes]
-
A.
hasEvacuationZone
chosen
Indicates that a specified area or location falls within a designated evacuation zone associated with another entity (such as an event, hazard, or authority).
-
B.
hasEmergencyPlanningZone
Indicates that an entity is associated with a designated emergency planning zone within which specific preparedness and response measures apply.
-
C.
hasEvacuationTarget
Indicates that an entity has a designated location or destination to which it should be evacuated in an emergency or contingency situation.
-
D.
evacuationZoneRadius_km
Indicates the distance, in kilometers, from a central point within which people or assets must be evacuated or kept clear.
-
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.