Triple
T26678235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coors Distributing Company |
E672524
|
entity |
| Predicate | handlesProductCategory |
P161603
|
FINISHED |
| Object | packaged beverages |
—
|
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: packaged beverages | Statement: [Coors Distributing Company, handlesProductCategory, packaged beverages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesProductCategory Context triple: [Coors Distributing Company, handlesProductCategory, packaged beverages]
-
A.
haveCategoryCode
Indicates that an entity is associated with a specific classification or category identified by a code.
-
B.
handlesCatalogOf
Indicates that one entity is responsible for managing, maintaining, or operating the catalog belonging to another entity.
-
C.
performsCategory
Indicates that an entity carries out or executes an action, task, or function that belongs to a specified category.
-
D.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
E.
sampleCategory
Indicates that an item or instance belongs to, or is classified under, a particular sample category.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61ad613608190855de13501a86007 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f61a16b7848190bf20d2be7e5a16c1 |
completed | May 2, 2026, 3:36 p.m. |
Created at: April 27, 2026, 3:18 a.m.