Triple
T31090703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Maybach GLS 600 |
E792375
|
entity |
| Predicate | luxuryPositioning |
P161527
|
FINISHED |
| Object | ultra-luxury SUV |
—
|
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: ultra-luxury SUV | Statement: [Mercedes-Maybach GLS 600, luxuryPositioning, ultra-luxury SUV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: luxuryPositioning Context triple: [Mercedes-Maybach GLS 600, luxuryPositioning, ultra-luxury SUV]
-
A.
luxuryOrientation
Indicates a tendency or strategic focus toward luxury, premium, or high-end qualities, experiences, or positioning.
-
B.
luxurySegment
Indicates that the associated entity belongs to, targets, or is positioned within the luxury or premium market segment.
-
C.
hasLuxuryPositioning
chosen
Indicates that an entity is positioned or marketed as a premium, high-end, or luxury offering relative to alternatives.
-
D.
isLuxuryGood
Indicates that an item is considered a high-end, non-essential product associated with premium quality, exclusivity, or status.
-
E.
luxuryFeatures
Indicates that the subject possesses or is associated with high-end, premium, or upscale features beyond standard functionality.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:02 p.m.