Triple
T14041662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Juan Parangaricutiro |
E337860
|
entity |
| Predicate | hasTypeOfDestruction |
P49010
|
FINISHED |
| Object | lava flow burial |
—
|
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: lava flow burial | Statement: [San Juan Parangaricutiro, hasTypeOfDestruction, lava flow burial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDestruction Context triple: [San Juan Parangaricutiro, hasTypeOfDestruction, lava flow burial]
-
A.
typeOfDestruction
chosen
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
B.
destructionStatus
Indicates the condition or extent to which something has been damaged, ruined, or rendered unusable.
-
C.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
D.
hasDemolitionOrDestruction
Indicates that one entity causes, undergoes, or is associated with the demolition or destruction of another entity.
-
E.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de311814e48190adb637e1c97c0658 |
completed | April 14, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.