Triple
T12439654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Family Secrets |
E297235
|
entity |
| Predicate | notableMurderCase |
P32047
|
FINISHED |
| Object | murder of Tony Spilotro |
—
|
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: murder of Tony Spilotro | Statement: [Operation Family Secrets, notableMurderCase, murder of Tony Spilotro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMurderCase Context triple: [Operation Family Secrets, notableMurderCase, murder of Tony Spilotro]
-
A.
notableSuspect
Indicates that an individual is a particularly significant or prominent suspect in relation to an event, case, or investigation.
-
B.
notableViolentCase
chosen
Indicates that an entity is associated with a specific case or incident that is recognized as involving significant or noteworthy violence.
-
C.
featuresMurderInvestigation
Indicates that the subject involves or includes a murder investigation as a central element or storyline.
-
D.
mysteryAssociatedWith
Indicates a relationship where something is connected to, involved in, or characterized by an element of mystery or the unknown.
-
E.
murders
Indicates that one entity unlawfully and intentionally kills another entity.
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.