Triple
T27803329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niuafoou |
E702305
|
entity |
| Predicate | hadEvacuation |
P96080
|
FINISHED |
| Object | 1946 evacuation to ʻEua and Tongatapu |
—
|
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: 1946 evacuation to ʻEua and Tongatapu | Statement: [Niuafoou, hadEvacuation, 1946 evacuation to ʻEua and Tongatapu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadEvacuation Context triple: [Niuafoou, hadEvacuation, 1946 evacuation to ʻEua and Tongatapu]
-
A.
evacuatedDuring
Indicates that one entity was removed or relocated from a place or situation during the time period or event represented by the other entity.
-
B.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
C.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
-
D.
hasEvacuationHistory
chosen
Indicates that an entity has previously undergone or been involved in one or more evacuation events.
-
E.
evacuationOrderedIn
Indicates that an official evacuation has been ordered to occur within a specified location or area.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63837d8c881908afb5ff38b4bee73 |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:36 p.m.