Triple
T4431767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enstone-based Formula One facility |
E95346
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Formula One team factory |
C14025
|
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 team factory Context triple: [Enstone-based Formula One facility, instanceOf, Formula One team factory]
-
A.
Formula One team
chosen
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.
-
B.
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.
-
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 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.
-
E.
stock car racing team
A stock car racing team is an organized group that prepares, maintains, and races stock cars in competitive motorsport events, coordinating drivers, mechanics, engineers, and support staff to achieve success on the track.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:31 p.m.