Triple
T16801933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasury Wine Estates |
E408376
|
entity |
| Predicate | keyBrandCategory |
P39625
|
FINISHED |
| Object | luxury wine |
—
|
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: luxury wine | Statement: [Treasury Wine Estates, keyBrandCategory, luxury wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyBrandCategory Context triple: [Treasury Wine Estates, keyBrandCategory, luxury wine]
-
A.
associatedBrandCategory
chosen
Indicates that a brand is linked to or classified under a particular product or service category.
-
B.
brandSegment
Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
-
C.
brandAssociationType
Indicates the specific nature of the relationship or association that exists between a brand and another entity (such as a product, organization, or campaign).
-
D.
brandFocus
Indicates that a brand primarily concentrates its efforts, messaging, or resources on a particular target, theme, or market segment.
-
E.
brandingFeature
Indicates that one entity serves as a branding-related characteristic, element, or attribute that helps define or distinguish another entity’s brand identity.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2c8fe58819087d3b83635255c34 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.