Triple
T3738619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula One (as team owner) |
E79645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational role in Formula One |
C12329
|
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: organizational role in Formula One Context triple: [Formula One (as team owner), instanceOf, organizational role in Formula One]
-
A.
sports governance role
chosen
A sports governance role is a position responsible for overseeing the rules, policies, integrity, and strategic direction of sports organizations or competitions.
-
B.
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.
-
C.
racing driver
A racing driver is a professional or amateur competitor who operates high-performance vehicles at speed in organized motorsport events, applying advanced driving skills, strategy, and physical endurance to achieve the fastest possible lap times and race results.
-
D.
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.
-
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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:34 p.m.