Triple
T33405961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Racing Performance Parts |
E855438
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive performance parts brand |
C58574
|
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: automotive performance parts brand Context triple: [Ford Racing Performance Parts, instanceOf, automotive performance parts brand]
-
A.
aftermarket parts brand
chosen
An aftermarket parts brand is a company that designs, manufactures, and sells non-original replacement or performance-enhancing components for vehicles or equipment, typically offering alternatives to OEM parts.
-
B.
automotive parts retailer brand
A brand that specializes in selling a wide range of automotive parts and accessories to consumers and repair professionals, emphasizing reliability, availability, and vehicle-specific expertise.
-
C.
BMW M Performance Parts range
The BMW M Performance Parts range is a collection of factory-engineered, motorsport-inspired components and accessories designed to enhance the performance, aesthetics, and driving dynamics of BMW vehicles.
-
D.
automotive brand
An automotive brand is a conceptual entity representing the identity, reputation, and market presence of a manufacturer that designs, produces, and sells motor vehicles under a distinct name and image.
-
E.
racing engine manufacturer
A racing engine manufacturer is a company that designs, develops, and produces high-performance engines specifically optimized for competitive motorsport applications.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.