Triple
T18105066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Gardens subdivision (by lava flows) |
E433327
|
entity |
| Predicate | typeOfDisasterImpact |
P124172
|
FINISHED |
| Object | complete burial by lava |
—
|
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: complete burial by lava | Statement: [Royal Gardens subdivision (by lava flows), typeOfDisasterImpact, complete burial by lava]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDisasterImpact Context triple: [Royal Gardens subdivision (by lava flows), typeOfDisasterImpact, complete burial by lava]
-
A.
impactOfDisasters
chosen
Indicates the effects or consequences that disasters have on entities, conditions, or outcomes.
-
B.
causeOfDisaster
Indicates that the subject is responsible for bringing about or triggering the specified disaster.
-
C.
infrastructureDamage
Indicates damage or destruction affecting physical infrastructure such as buildings, roads, utilities, or other constructed facilities.
-
D.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
E.
notableDisasterType
Indicates the specific kind or category of disaster for which something (such as a place, event, or entity) is notable or best known.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb9981c8190b33697fbcaa901b3 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.