Triple
T13290732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1950 Formula One World Championship |
E316553
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Formula One World Championship season |
C32785
|
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: Formula One World Championship season Context triple: [1950 Formula One World Championship, instanceOf, Formula One World Championship season]
-
A.
Formula One Grand Prix
A Formula One Grand Prix is a premier international motor racing event, held on a designated circuit or street track, where teams and drivers compete in highly engineered single-seater cars for championship points.
-
B.
Formula One racing car
A Formula One racing car is a highly specialized, open-wheel, single-seat vehicle engineered for maximum speed, agility, and performance under strict FIA regulations in top-tier motorsport competition.
-
C.
Formula One circuit
A Formula One circuit is a specialized racing track, either permanent or temporary, designed and certified to host Formula One Grand Prix events, featuring complex layouts, safety features, and facilities for teams, officials, and spectators.
-
D.
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.
-
E.
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.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:27 p.m.