Triple
T8637534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astroworld Festival |
E204559
|
entity |
| Predicate | injuriesIn2021Incident |
P25887
|
FINISHED |
| Object | hundreds of injuries |
—
|
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: hundreds of injuries | Statement: [Astroworld Festival, injuriesIn2021Incident, hundreds of injuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: injuriesIn2021Incident Context triple: [Astroworld Festival, injuriesIn2021Incident, hundreds of injuries]
-
A.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
B.
injuriesApprox
chosen
Indicates an approximate or estimated number or extent of injuries associated with an event or entity.
-
C.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
D.
injuryType
Indicates the specific kind or category of injury associated with an entity or event.
-
E.
injuryDate
Indicates the date on which an injury occurred or was sustained.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:28 p.m.