Triple
T16568492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salafist Group for Preaching and Combat |
E402523
|
entity |
| Predicate | usedFundingMethods |
P124091
|
FINISHED |
| Object | smuggling |
—
|
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: smuggling | Statement: [Salafist Group for Preaching and Combat, usedFundingMethods, smuggling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFundingMethods Context triple: [Salafist Group for Preaching and Combat, usedFundingMethods, smuggling]
-
A.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
B.
paymentMethod
Indicates the means or instrument through which a payment is made in a transaction.
-
C.
supportsAllocationMethods
Indicates that one entity enables, is compatible with, or provides mechanisms for using specific allocation methods associated with another entity.
-
D.
paymentServices
Indicates that one entity provides or facilitates payment-related services or processing for another entity.
-
E.
usedFeederFunds
Indicates that an entity employed feeder funds as intermediary investment vehicles to channel capital into another fund or investment structure.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35773c00c819091731bebc02a69bb |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:16 a.m.