Triple
T27871958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oga Garra |
E704812
|
entity |
| Predicate | businessFrontFor |
P94881
|
FINISHED |
| Object | criminal activities |
—
|
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: criminal activities | Statement: [Oga Garra, businessFrontFor, criminal activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessFrontFor Context triple: [Oga Garra, businessFrontFor, criminal activities]
-
A.
frontBusiness
chosen
Indicates that one entity operates as a façade or cover business for another entity, typically concealing the latter’s true activities or identity.
-
B.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
C.
businessVenture
Indicates a relationship where entities jointly engage in, operate, or are involved with a commercial or entrepreneurial undertaking.
-
D.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
-
E.
businessForm
Indicates the legal or organizational structure under which a business operates (e.g., sole proprietorship, partnership, corporation).
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 6:25 p.m.