Triple
T28283330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartel of the Suns |
E713211
|
entity |
| Predicate | allegedAllies |
P136406
|
FINISHED |
| Object | Colombian drug trafficking organizations |
—
|
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: Colombian drug trafficking organizations | Statement: [Cartel of the Suns, allegedAllies, Colombian drug trafficking organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedAllies Context triple: [Cartel of the Suns, allegedAllies, Colombian drug trafficking organizations]
-
A.
alliesOf
chosen
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
-
B.
alliedAgainstBy
Indicates that the subject is opposed by an entity that has formed an alliance with others against it.
-
C.
alliesIncluded
Indicates that the specified set or group explicitly includes one or more allied entities as members.
-
D.
allegedCompanions
Indicates that two or more entities are claimed or reported to have been companions or associates, without confirming the truth of that relationship.
-
E.
formerAllyOf
Indicates that an entity was once an ally of another entity but that alliance has since ended.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 11:24 p.m.