Triple
T17984814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chenega, Alaska |
E430201
|
entity |
| Predicate | relocationAfterDisaster |
P11175
|
FINISHED |
| Object | residents relocated after 1964 tsunami |
—
|
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: residents relocated after 1964 tsunami | Statement: [Chenega, Alaska, relocationAfterDisaster, residents relocated after 1964 tsunami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationAfterDisaster Context triple: [Chenega, Alaska, relocationAfterDisaster, residents relocated after 1964 tsunami]
-
A.
impactOfDisasters
Indicates the effects or consequences that disasters have on entities, conditions, or outcomes.
-
B.
postDisasterRole
Indicates the role or function an entity assumes or performs in the aftermath of a disaster.
-
C.
disasterLocation
Indicates the place where a disaster occurs or has its primary impact.
-
D.
residenceAfterFlood
Indicates that an entity’s place of residence is the one occupied after a flood event has occurred.
-
E.
relocated
chosen
Indicates that an entity has moved or been moved from one location or position to another.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29a27b081909a128a6b978eabf8 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.