Triple
T38687014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 326 cu in Pontiac V8 |
E949145
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pontiac V8 engine family member |
C32185
|
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: Pontiac V8 engine family member Context triple: [326 cu in Pontiac V8, instanceOf, Pontiac V8 engine family member]
-
A.
Pontiac engine option
chosen
A Pontiac engine option is a specific factory-available powertrain configuration, defined by displacement, performance characteristics, and associated components, that buyers could select when ordering a Pontiac vehicle.
-
B.
Chevrolet small-block engine
The Chevrolet small-block engine is a family of compact, lightweight V8 internal combustion engines renowned for their durability, performance potential, and widespread use in Chevrolet vehicles and motorsports since the mid-20th century.
-
C.
GMC small-block engine
A GMC small-block engine is a compact, lightweight V8 internal combustion engine family known for its versatility, durability, and widespread use in GMC trucks and performance vehicles.
-
D.
Ford small-block engine
A Ford small-block engine is a family of compact, lightweight V8 internal combustion engines produced by Ford Motor Company, widely used in passenger cars and light trucks from the early 1960s through the 1990s.
-
E.
Pontiac Tempest model variant
A Pontiac Tempest model variant is a specific configuration of the Tempest automobile distinguished by particular combinations of body style, engine, trim, and features offered in a given model year.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.