Triple
T13525976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota works drivers |
E323017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of professional racing drivers |
C33152
|
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: group of professional racing drivers Context triple: [Toyota works drivers, instanceOf, group of professional racing drivers]
-
A.
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.
-
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.
racing car constructor
A racing car constructor is an organization that designs, engineers, builds, and develops competitive race cars, often for participation in professional motorsport series.
-
D.
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.
-
E.
factory-backed motorsport team
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.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.