Triple
T16397341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeta |
E398215
|
entity |
| Predicate | postDisasterChange |
P60365
|
FINISHED |
| Object | increased resettlement in lowland areas |
—
|
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: increased resettlement in lowland areas | Statement: [Aeta, postDisasterChange, increased resettlement in lowland areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postDisasterChange Context triple: [Aeta, postDisasterChange, increased resettlement in lowland areas]
-
A.
postDisasterStatus
chosen
Indicates the condition or state of an entity following the occurrence of a disaster.
-
B.
postDisasterRole
Indicates the role or function an entity assumes or performs in the aftermath of a disaster.
-
C.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
D.
causeOfDisaster
Indicates that the subject is responsible for bringing about or triggering the specified disaster.
-
E.
disasterDepicted
Indicates that one entity visually represents or portrays a disaster involving or affecting another entity.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cc5c9c8190ba1a70f9e430cefb |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.