Triple
T35352296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miyakejima |
E1020916
|
entity |
| Predicate | evacuationOrdered |
P87487
|
FINISHED |
| Object | September 2000 |
—
|
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: September 2000 | Statement: [Miyakejima, evacuationOrdered, September 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuationOrdered Context triple: [Miyakejima, evacuationOrdered, September 2000]
-
A.
evacuationOrderedIn
chosen
Indicates that an official evacuation has been ordered to occur within a specified location or area.
-
B.
evacuationOrderedAfter
Indicates that an evacuation is officially ordered as a consequence of, and subsequent to, a specified prior event or condition.
-
C.
evacuationOrderIssuedBy
Indicates that a specific authority or organization has formally issued an evacuation order for people to leave a particular area.
-
D.
evacuationOrderLifted
Indicates that a previously issued evacuation order has been officially canceled, allowing people to return to the affected area.
-
E.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.