Triple
T9429155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altamont Free Concert |
E227328
|
entity |
| Predicate | causeOfMainDeath |
P144
|
FINISHED |
| Object | stabbing by Hells Angels member |
—
|
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: stabbing by Hells Angels member | Statement: [Altamont Free Concert, causeOfMainDeath, stabbing by Hells Angels member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfMainDeath Context triple: [Altamont Free Concert, causeOfMainDeath, stabbing by Hells Angels member]
-
A.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
B.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
C.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
-
D.
reasonForDemise
Indicates the cause, circumstance, or factor that led to an entity’s death or termination.
-
E.
mourningCause
Indicates that one entity is in a state of mourning specifically because of the other entity, which is the cause or reason for the grief.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7c94719c81909d7743a57c45e07f |
completed | April 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.