Triple
T11572761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manson Family (in-universe events) |
E274430
|
entity |
| Predicate | involvesCrimeType |
P7957
|
FINISHED |
| Object | attempted mass murder |
—
|
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: attempted mass murder | Statement: [Manson Family (in-universe events), involvesCrimeType, attempted mass murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesCrimeType Context triple: [Manson Family (in-universe events), involvesCrimeType, attempted mass murder]
-
A.
crimeType
chosen
Indicates the specific category or nature of the crime associated with an event or entity.
-
B.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
C.
crimeCharged
Indicates that legal authorities have formally accused an entity of committing a specific crime.
-
D.
pursuesCrimeType
Indicates that an entity (such as a law enforcement body or individual) actively investigates, targets, or prosecutes a specified type of crime.
-
E.
criminalType
Indicates the specific category or classification of crime associated with a criminal act or offender.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd6913881908becf188c0a7a275 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.