Triple
T13443196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polestar |
E320415
|
entity |
| Predicate | hasSalesModel |
P19968
|
FINISHED |
| Object | direct-to-consumer sales |
—
|
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: direct-to-consumer sales | Statement: [Polestar, hasSalesModel, direct-to-consumer sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSalesModel Context triple: [Polestar, hasSalesModel, direct-to-consumer sales]
-
A.
hasModelSeries
Indicates a relationship where an item or product is associated with a specific model series it belongs to.
-
B.
hasRealModel
Indicates that an abstract, theoretical, or simplified entity is associated with a corresponding concrete or physically instantiated model in the real world.
-
C.
hasFranchiseModel
Indicates that one entity operates under, offers, or is associated with a business franchise system or structure defined by another entity.
-
D.
hasCareModel
Indicates that one entity uses, follows, or is governed by a particular model or approach to providing care.
-
E.
hasReleaseModel
chosen
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee881888190811ddf01bc699864 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.