Triple
T21086467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Tambora |
E519500
|
entity |
| Predicate | demiseType |
P54293
|
FINISHED |
| Object | sudden catastrophic destruction |
—
|
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: sudden catastrophic destruction | Statement: [Kingdom of Tambora, demiseType, sudden catastrophic destruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demiseType Context triple: [Kingdom of Tambora, demiseType, sudden catastrophic destruction]
-
A.
deathRecordType
Indicates the specific category or classification of a recorded death event within a death record system.
-
B.
reasonForDemise
Indicates the cause, circumstance, or factor that led to an entity’s death or termination.
-
C.
deathCharacteristic
chosen
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
-
D.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
E.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094ad1c08190a4b9d2668a6362b2 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.