Triple
T29502819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tassimo |
E748419
|
entity |
| Predicate | supportsBeverageType |
—
|
GENERATED |
| Object | coffee |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBeverageType Context triple: [Tassimo, supportsBeverageType, coffee]
-
A.
hasBeverageProduct
Indicates that one entity possesses, offers, or is associated with a particular beverage product.
-
B.
hasBeverageCategory
chosen
Indicates that an entity is associated with or classified under a particular beverage category.
-
C.
hasBeverageReference
Indicates that one entity makes reference to, mentions, or is associated with a beverage in some way.
-
D.
hasBeveragePolicy
Indicates that an entity has an established rule or set of guidelines governing the provision, consumption, or management of beverages.
-
E.
hasBeverageProgram
Indicates that an entity offers, manages, or participates in an organized beverage-related offering or initiative.
- F. None of above.
Provenance (1 batch)
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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:25 p.m.