Triple
T21846583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dennis Allen |
E539389
|
entity |
| Predicate | criminalNetwork |
P21640
|
FINISHED |
| Object | Melbourne-based drug distribution network |
—
|
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: Melbourne-based drug distribution network | Statement: [Dennis Allen, criminalNetwork, Melbourne-based drug distribution network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criminalNetwork Context triple: [Dennis Allen, criminalNetwork, Melbourne-based drug distribution network]
-
A.
criminalOrganization
chosen
Indicates that the subject is an organized group engaged in ongoing illegal activities, often with structured hierarchy and coordination.
-
B.
criminalType
Indicates the specific category or classification of crime associated with a criminal act or offender.
-
C.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
D.
crimeType
Indicates the specific category or nature of the crime associated with an event or entity.
-
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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd546fb48190a7b815233650c2e7 |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.