Triple
T26678228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coors Distributing Company |
E672524
|
entity |
| Predicate | distributesBrand |
P37853
|
FINISHED |
| Object | Coors |
—
|
NE NERFINISHED |
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: Coors | Statement: [Coors Distributing Company, distributesBrand, Coors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributesBrand Context triple: [Coors Distributing Company, distributesBrand, Coors]
-
A.
distributedBrand
chosen
Indicates that one entity serves as a distributor or reseller for the brand of another entity.
-
B.
distributesIn
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
-
C.
distributesFrom
Indicates that something acts as the source or origin from which items, resources, or information are distributed to others.
-
D.
distributionFor
Indicates a relationship where one entity serves as the distribution, delivery, or dissemination mechanism for another entity.
-
E.
catalogBrand
Indicates that a brand is associated with, or offered within, a particular catalog.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:18 a.m.