Triple
T30522574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brownsville Boys |
E776737
|
entity |
| Predicate | roleInOrganizedCrime |
P155066
|
FINISHED |
| Object | enforcement arm |
—
|
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: enforcement arm | Statement: [Brownsville Boys, roleInOrganizedCrime, enforcement arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInOrganizedCrime Context triple: [Brownsville Boys, roleInOrganizedCrime, enforcement arm]
-
A.
roleInCrime
Indicates the specific function, responsibility, or participation an entity has within the commission of a particular crime.
-
B.
criminalOrganization
Indicates that the subject is an organized group engaged in ongoing illegal activities, often with structured hierarchy and coordination.
-
C.
hasOrganizedCrimeTheme
Indicates that the subject’s content, narrative, or context centrally involves organized crime activities, groups, or structures.
-
D.
roleInGangRelated
chosen
Indicates that an entity holds a specific role or function within a gang-related context or activity.
-
E.
partnerInCrime
Indicates a relationship where two or more entities collaborate closely in committing or planning wrongful, illicit, or mischievous acts together.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: April 29, 2026, 8:17 p.m.