Triple
T16773455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champlain Towers South condominium |
E407661
|
entity |
| Predicate | collapseType |
P124580
|
FINISHED |
| Object | partial progressive collapse |
—
|
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: partial progressive collapse | Statement: [Champlain Towers South condominium, collapseType, partial progressive collapse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collapseType Context triple: [Champlain Towers South condominium, collapseType, partial progressive collapse]
-
A.
collapseEvent
Indicates an event in which a structure, system, or entity suddenly falls apart, fails, or loses its integrity.
-
B.
collapsedDueTo
Indicates that one entity fell down, caved in, or structurally failed as a result of another specified cause or factor.
-
C.
collapsedOn
Indicates that one entity physically fell or caved in onto another entity, ending up resting on or covering it.
-
D.
collapsedWith
Indicates that one entity fell down or caved in together with another entity, typically as part of the same collapse event.
-
E.
collapsedAfter
Indicates that one entity collapsed at some point in time after another specified event or entity’s collapse.
- F. None of above. chosen
Provenance (4 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b037c5708190ba604e7707b5a8a2 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.