Triple
T37396116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proposition Joe’s Eastside crew |
E928857
|
entity |
| Predicate | sourceOfSupply |
P138584
|
FINISHED |
| Object | high-quality heroin |
—
|
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: high-quality heroin | Statement: [Proposition Joe’s Eastside crew, sourceOfSupply, high-quality heroin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceOfSupply Context triple: [Proposition Joe’s Eastside crew, sourceOfSupply, high-quality heroin]
-
A.
supplyRole
Indicates that an entity provides or fulfills a specific role within a supply or provisioning relationship to another entity.
-
B.
supplyType
Indicates the kind or category of supply associated with or provided in a given relationship or context.
-
C.
supplyMode
Indicates the manner or method by which something is provided, delivered, or made available.
-
D.
supplierType
Indicates the classification or category of a supplier based on its role or characteristics in a supply relationship.
-
E.
supplyBy
chosen
Indicates that one entity is provided, furnished, or made available by another entity as its source or supplier.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:16 p.m.