Triple
T36970399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuélap archaeological site |
E914548
|
entity |
| Predicate | roofCollapseEvent |
P58737
|
FINISHED |
| Object | April 2022 |
—
|
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: April 2022 | Statement: [Kuélap archaeological site, roofCollapseEvent, April 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofCollapseEvent Context triple: [Kuélap archaeological site, roofCollapseEvent, April 2022]
-
A.
roofCollapsed
chosen
Indicates that the roof of a structure has given way or fallen in, typically due to structural failure or external forces.
-
B.
causedBuildingCollapse
Indicates that one entity was responsible for bringing about the structural failure or collapse of a building.
-
C.
towerCollapsedIn
Indicates that a tower underwent structural failure and collapsed at or within a specified location or context.
-
D.
naturalCaveCollapsed
Indicates that a naturally formed cave has undergone a structural failure resulting in its partial or complete collapse.
-
E.
ceilingCollapseFatalities
Indicates that a ceiling collapse event resulted in one or more fatalities.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.