Triple
T36020474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iriga Volcano |
E1041966
|
entity |
| Predicate | hasDestructiveEvent |
P199901
|
FINISHED |
| Object | historic landslides |
—
|
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: historic landslides | Statement: [Iriga Volcano, hasDestructiveEvent, historic landslides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDestructiveEvent Context triple: [Iriga Volcano, hasDestructiveEvent, historic landslides]
-
A.
hasDeterminingEvent
Indicates that one event or occurrence serves as the decisive cause, condition, or basis that determines another situation, outcome, or state.
-
B.
hasFireEvent
Indicates that a fire-related incident or occurrence is associated with, or has taken place involving, a given entity.
-
C.
hasDedicatedEvent
Indicates that a specific event is explicitly organized or reserved for the referenced entity or relationship.
-
D.
hasPrimaryEvent
Indicates that an entity is associated with or linked to its main or most significant event.
-
E.
hasSideEvent
Indicates that an event is associated with an additional, related side event occurring alongside it.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69ff632176b0819084610ae2e57ab679 |
completed | May 9, 2026, 4:38 p.m. |
Created at: May 3, 2026, 4:07 p.m.