Triple
T3428130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skagen |
E72273
|
entity |
| Predicate | hasBrandPositioning |
P5254
|
FINISHED |
| Object | affordable luxury |
—
|
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: affordable luxury | Statement: [Skagen, hasBrandPositioning, affordable luxury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandPositioning Context triple: [Skagen, hasBrandPositioning, affordable luxury]
-
A.
brandPositioning
chosen
Indicates how a brand is strategically placed and perceived in the minds of its target audience relative to competitors.
-
B.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
C.
isPartOfBrandStrategy
Indicates that an action, element, or decision is included within and contributes to the overall brand strategy.
-
D.
hasGlobalBrand
Indicates that an entity possesses a brand that is recognized and operates across multiple countries or worldwide.
-
E.
brandingStatus
Indicates the current state or condition of an entity’s branding, such as whether its brand identity has been defined, applied, updated, or is pending.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb983f4608190abcc27aa7b926deb |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.