Triple
T26897219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evacuation during Dark Sea flood |
E677926
|
entity |
| Predicate | evacuatedGroup |
P161312
|
FINISHED |
| Object | citizens of Arendelle |
—
|
NE NERFINISHED |
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: citizens of Arendelle | Statement: [Evacuation during Dark Sea flood, evacuatedGroup, citizens of Arendelle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuatedGroup Context triple: [Evacuation during Dark Sea flood, evacuatedGroup, citizens of Arendelle]
-
A.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
B.
evacuatedUnit
Indicates that a unit has been removed from a location or situation, typically for safety or strategic reasons.
-
C.
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.
-
D.
evacueeCategory
Indicates the classification assigned to an evacuee based on their status, needs, or priority during an evacuation.
-
E.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
- F. None of above. chosen
Provenance (4 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fac4c808190a27f121fac4fe61c |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 5:48 a.m.