Triple
T23799094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gui-ob Church Ruins |
E588619
|
entity |
| Predicate | causeOfRuins |
P26452
|
FINISHED |
| Object | volcanic eruption |
—
|
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: volcanic eruption | Statement: [Gui-ob Church Ruins, causeOfRuins, volcanic eruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfRuins Context triple: [Gui-ob Church Ruins, causeOfRuins, volcanic eruption]
-
A.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
B.
causeOfDownfall
chosen
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
C.
causeOfDisaster
Indicates that the subject is responsible for bringing about or triggering the specified disaster.
-
D.
disasterCauseDetail
Indicates a detailed explanation of the specific cause or contributing factors behind a disaster.
-
E.
consequenceOfDestruction
Indicates that one event, state, or condition occurs as a direct result of a prior act of destruction.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6dfaae081908be48fa89e625f71 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:51 p.m.