Triple
T31602528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joffrey’s Coffee & Tea Company |
E806383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialty coffee brand |
C10328
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: specialty coffee brand Context triple: [Joffrey’s Coffee & Tea Company, instanceOf, specialty coffee brand]
-
A.
self-service coffee bar brand
A self-service coffee bar brand offers a convenient, streamlined experience where customers independently select, customize, and dispense high-quality coffee and related beverages in a branded, often automated environment.
-
B.
pod coffee supplier
A pod coffee supplier is a business that sources, packages, and distributes single-serve coffee pods to consumers, retailers, or offices, often offering a variety of blends, flavors, and compatible formats for different pod-based brewing systems.
-
C.
coffeehouse
A coffeehouse is a social establishment where people gather to purchase and enjoy coffee, other beverages, and light food in a relaxed, often communal atmosphere.
-
D.
beverage brand
chosen
A beverage brand is a distinct identity under which drinks are marketed, characterized by unique naming, visual design, positioning, and perceived qualities that differentiate its products in the marketplace.
-
E.
in-store café brand
An in-store café brand is a distinct, cohesive identity for a café located within a larger retail environment, designed to enhance the shopping experience and drive customer loyalty through food, beverages, and ambiance aligned with the host store’s values.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:33 p.m.