Triple
T32402309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armero tragedy |
E827984
|
entity |
| Predicate | missingPersonsApprox |
P87238
|
FINISHED |
| Object | thousands |
—
|
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: thousands | Statement: [Armero tragedy, missingPersonsApprox, thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missingPersonsApprox Context triple: [Armero tragedy, missingPersonsApprox, thousands]
-
A.
missingPersonsEstimate
chosen
Indicates an estimated number of people who are unaccounted for or reported missing in a given context or event.
-
B.
hasMissingPersonCase
Indicates that an entity is involved in or associated with a missing person case.
-
C.
placeOfDisappearance
Indicates the location where an entity was last seen or went missing.
-
D.
intendedDestinationAtTimeOfDisappearance
Indicates the location or place an entity was planning to go to at the specific time when it disappeared.
-
E.
numberOfUnidentifiedRemains
Indicates the count of human remains that have not yet been identified in a given context or case.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 12:52 a.m.