Triple
T32402298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armero tragedy |
E827984
|
entity |
| Predicate | buriedTown |
P168524
|
FINISHED |
| Object | Armero |
—
|
NE NERFINISHED |
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: Armero | Statement: [Armero tragedy, buriedTown, Armero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buriedTown Context triple: [Armero tragedy, buriedTown, Armero]
-
A.
buriedUnder
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
B.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
C.
buriedDuring
chosen
Indicates that one entity was buried during the time period or event associated with another entity.
-
D.
fellAndBuried
Indicates that one entity fell and consequently became buried, typically under some material or surface.
-
E.
buriedAs
Indicates that one entity is interred or laid to rest in the manner, role, or context specified by 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c21bb0d081909644ca365aacfdfa |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:52 a.m.