Triple
T28717662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mullens gang |
E730004
|
entity |
| Predicate | criminalUnderworldRole |
P62350
|
FINISHED |
| Object | rival to other South Boston gangs |
—
|
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: rival to other South Boston gangs | Statement: [Mullens gang, criminalUnderworldRole, rival to other South Boston gangs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criminalUnderworldRole Context triple: [Mullens gang, criminalUnderworldRole, rival to other South Boston gangs]
-
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.
roleInDa5Bloods
Indicates that an entity had an acting role in the film "Da 5 Bloods."
-
D.
roleInGangRelated
Indicates that an entity holds a specific role or function within a gang-related context or activity.
-
E.
roleInGang
chosen
Indicates that an entity holds a specific position or function within a gang organization.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65706d96081909df278575e3c67f0 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:51 a.m.