Triple
T17176475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 Aggie Bonfire collapse |
E416873
|
entity |
| Predicate | stackHeightAtCollapse |
P44247
|
FINISHED |
| Object | approximately 59 feet |
—
|
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: approximately 59 feet | Statement: [1999 Aggie Bonfire collapse, stackHeightAtCollapse, approximately 59 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stackHeightAtCollapse Context triple: [1999 Aggie Bonfire collapse, stackHeightAtCollapse, approximately 59 feet]
-
A.
elevationBeforeCollapse
Indicates that one entity’s elevation value is measured or defined as it was prior to a collapse event affecting that entity or its supporting structure.
-
B.
structureHeight
chosen
Indicates that a structure has a specific vertical measurement or height.
-
C.
numberOfStacks
Indicates the count of distinct stacks associated with or contained within a given entity.
-
D.
maxStackSize
Indicates the maximum number of identical items or elements that can be grouped or stacked together as a single unit.
-
E.
dropHeight
Indicates the vertical distance from which an object is released or allowed to fall.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0e14e08190901b1fbccc9322ae |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.