Triple
T24197832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medellín Cartel |
E599881
|
entity |
| Predicate | launderingMethod |
P155147
|
FINISHED |
| Object | front companies |
—
|
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: front companies | Statement: [Medellín Cartel, launderingMethod, front companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launderingMethod Context triple: [Medellín Cartel, launderingMethod, front companies]
-
A.
numberOfWashings
Indicates the count of times a washing or cleaning action has been performed on an entity.
-
B.
diversionMethod
Indicates the method or tactic used to distract, mislead, or redirect attention or resources away from a primary target or activity.
-
C.
antiMoneyLaunderingRegulator
Indicates that an entity serves as the authority responsible for overseeing and enforcing anti–money laundering regulations in relation to another entity or activity.
-
D.
typeOfPurification
Indicates the specific purification method or process applied to an entity or substance.
-
E.
smugglingMethod
Indicates the method or technique used to illegally transport goods or people across borders or through restricted areas.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24c103481908ea49dd8e77dee32 |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:36 p.m.