Triple
T13477018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-AMG Petronas Formula One Team |
E318275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mercedes-Benz motorsport team |
C15613
|
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: Mercedes-Benz motorsport team Context triple: [Mercedes-AMG Petronas Formula One Team, instanceOf, Mercedes-Benz motorsport team]
-
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.
Formula One team
A Formula One team is an organization that designs, builds, and races single-seater F1 cars in the FIA Formula One World Championship, managing drivers, engineering, strategy, and operations to compete at the highest level of motorsport.
-
C.
Formula One constructor
A Formula One constructor is an entity (team or manufacturer) that designs, builds, and enters its own F1 car chassis in the FIA Formula One World Championship.
-
D.
factory-backed motorsport team
chosen
A factory-backed motorsport team is a racing organization that receives direct financial, technical, and logistical support from an automobile manufacturer to develop and compete with its vehicles.
-
E.
Porsche one-make series
A Porsche one-make series is a racing championship in which all competitors drive identical Porsche models prepared to the same technical specifications, emphasizing driver skill over mechanical advantage.
- F. None of above.
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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:42 p.m.