Triple
T9234867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz GLS |
E221910
|
entity |
| Predicate | brandLineupPosition |
P18925
|
FINISHED |
| Object | top of Mercedes-Benz SUV range |
—
|
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: top of Mercedes-Benz SUV range | Statement: [Mercedes-Benz GLS, brandLineupPosition, top of Mercedes-Benz SUV range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandLineupPosition Context triple: [Mercedes-Benz GLS, brandLineupPosition, top of Mercedes-Benz SUV range]
-
A.
positionInBrandPortfolio
Indicates the relative role or rank that a brand holds within a company’s overall brand portfolio.
-
B.
positionInProductLine
Indicates the specific place or order an item occupies within a defined product line or series.
-
C.
positionInLineup
chosen
Indicates the specific ordered place an entity occupies within a lineup or sequence of entities.
-
D.
brandLine
Indicates that one brand is a specific product line or sub-brand offered under another brand.
-
E.
brandPositioning
Indicates how a brand is strategically placed and perceived in the minds of its target audience relative to competitors.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee1cca0c8190bf587f54236c9e45 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:29 p.m.