Triple
T20486114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Cosa Nostra |
E502596
|
entity |
| Predicate | notableCriminalActivityType |
P96742
|
FINISHED |
| Object | infiltration of labor unions |
—
|
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: infiltration of labor unions | Statement: [American Cosa Nostra, notableCriminalActivityType, infiltration of labor unions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCriminalActivityType Context triple: [American Cosa Nostra, notableCriminalActivityType, infiltration of labor unions]
-
A.
criminalType
chosen
Indicates the specific category or classification of crime associated with a criminal act or offender.
-
B.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
-
C.
crimeType
Indicates the specific category or nature of the crime associated with an event or entity.
-
D.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
E.
notableHeistType
Indicates that the subject is notably associated with a specific type or category of heist.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b5aac208190956c7fd935578d60 |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:34 a.m.