Triple
T15535960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brewis |
E370342
|
entity |
| Predicate | illegalActivity |
P54348
|
FINISHED |
| Object | drug dealing |
—
|
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: drug dealing | Statement: [Brewis, illegalActivity, drug dealing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: illegalActivity Context triple: [Brewis, illegalActivity, drug dealing]
-
A.
illegalActivityAssociatedWith
chosen
Indicates that there is a connection between an entity and an unlawful or criminal activity.
-
B.
illegalMarket
Indicates a market relationship where goods or services are traded in violation of laws or regulations.
-
C.
protectedActivity
Indicates that an entity is engaged in an action or behavior that is legally or formally safeguarded from retaliation, interference, or adverse consequences.
-
D.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
E.
misuseCanConstitute
Indicates that improper or incorrect use of something can amount to, or be considered as, a particular offense, violation, or condition.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.