Triple
T35248748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Marcello et al. (Family Secrets) |
E1018037
|
entity |
| Predicate | involvesCrimeFamily |
P195872
|
FINISHED |
| Object | Chicago Outfit |
—
|
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: Chicago Outfit | Statement: [United States v. Marcello et al. (Family Secrets), involvesCrimeFamily, Chicago Outfit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesCrimeFamily Context triple: [United States v. Marcello et al. (Family Secrets), involvesCrimeFamily, Chicago Outfit]
-
A.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
B.
crimeType
Indicates the specific category or nature of the crime associated with an event or entity.
-
C.
criminalType
Indicates the specific category or classification of crime associated with a criminal act or offender.
-
D.
crimeAgainst
Indicates that one entity commits or is responsible for a criminal act directed toward another entity.
-
E.
criminalFront
Indicates a relationship where one entity secretly operates as a cover or façade to conceal the illegal activities of another entity.
- F. None of above. chosen
Provenance (4 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
| PDg | Predicate description generation | batch_69fdec5f0420819087c0230ad384c4ba |
completed | May 8, 2026, 1:59 p.m. |
Created at: May 3, 2026, 4:02 p.m.