Triple
T36011992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polestar Racing |
E1041736
|
entity |
| Predicate | affiliatedManufacturer |
P119866
|
FINISHED |
| Object | Volvo Cars |
—
|
NE NERFINISHED |
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: Volvo Cars | Statement: [Polestar Racing, affiliatedManufacturer, Volvo Cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliatedManufacturer Context triple: [Polestar Racing, affiliatedManufacturer, Volvo Cars]
-
A.
manufacturerAssociation
chosen
Indicates a relationship where one entity is associated with another in the role of manufacturer, typically responsible for producing or making the associated item.
-
B.
usedManufacturer
Indicates that an entity has employed or sourced products, components, or services from a particular manufacturer.
-
C.
formerManufacturerPartner
Indicates that two entities were previously in a manufacturer–partner business relationship, but that partnership has since ended.
-
D.
manufacturerType
Indicates the classification or category of a manufacturer based on its role, characteristics, or production type.
-
E.
manufacturedBy
Indicates that an item or product is produced or created by a specific manufacturer or maker.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acb462e88190b6429ca5e8c7bb73 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.