Triple
T18379779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renault Sport (historical) |
E446412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renault division |
C40433
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Renault division Context triple: [Renault Sport (historical), instanceOf, Renault division]
-
A.
Mercedes-Benz division
A Mercedes-Benz division is an organizational unit within the Mercedes-Benz company responsible for a specific product line, market segment, or operational function, such as passenger cars, commercial vehicles, or financial services.
-
B.
division of BMW
A division of BMW is an organizational unit within the BMW Group responsible for a specific product line, market segment, or business function, such as BMW, MINI, or BMW Motorrad.
-
C.
Opel brand division
The Opel brand division represents the organizational unit within an automotive company responsible for the design, production, marketing, and sales of vehicles under the Opel marque.
-
D.
Stellantis organizational unit
A Stellantis organizational unit is a defined structural entity within Stellantis responsible for specific functions, regions, brands, or business activities, operating under the company’s governance, processes, and strategic objectives.
-
E.
Citroën technology
Citroën technology encompasses the brand’s innovative automotive engineering solutions, including advanced suspension systems, distinctive design features, and integrated digital and safety technologies that enhance comfort, efficiency, and driving experience.
- F. None of above. chosen
Provenance (1 batch)
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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:45 a.m.