Triple
T34886123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sélection |
E1006147
|
entity |
| Predicate | brandTierWithinMigros |
P93352
|
FINISHED |
| Object | premium |
—
|
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: premium | Statement: [Sélection, brandTierWithinMigros, premium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandTierWithinMigros Context triple: [Sélection, brandTierWithinMigros, premium]
-
A.
brandLevel
chosen
Indicates the hierarchical rank or tier of a brand within a defined brand structure or classification system.
-
B.
brandScale
Indicates the extent or level of a brand’s size, reach, or influence within its market or context.
-
C.
premiumBrand
Indicates that one entity is recognized or classified as a high-end, premium-quality brand relative to others.
-
D.
merchantType
Indicates the category or classification of a merchant based on the type of goods or services they provide or the business model they operate under.
-
E.
isPremiumBrand
Indicates that a brand is classified as high-end or luxury, typically associated with superior quality, exclusivity, and higher price positioning compared to standard brands.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4 p.m.