Triple
T32155202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meredith Hunter |
E821267
|
entity |
| Predicate | killedByOrganization |
P4646
|
FINISHED |
| Object | Hells Angels Motorcycle Club |
—
|
NE NERFINISHED |
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: Hells Angels Motorcycle Club | Statement: [Meredith Hunter, killedByOrganization, Hells Angels Motorcycle Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killedByOrganization Context triple: [Meredith Hunter, killedByOrganization, Hells Angels Motorcycle Club]
-
A.
killedBy
chosen
Indicates that one entity caused the death of another entity.
-
B.
killedOnBehalfOf
Indicates that one entity carried out a killing as a representative of, or in service to, another entity.
-
C.
killedBecauseOf
Indicates that one entity killed another specifically due to a particular reason, motive, or triggering factor associated with that other entity or a related circumstance.
-
D.
killedByWeaponOf
Indicates that one entity was killed using a weapon that belongs to or is associated with another entity.
-
E.
killsOrIsKilledBy
Indicates that one entity causes the death of the other or is itself killed by that entity, capturing a mutual or directional lethal relationship between them.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9ee41a88190858b74a38adc8147 |
completed | May 3, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:32 a.m.