Triple
T21669970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodge Daytona (K-derivative) |
E534818
|
entity |
| Predicate | valvetrainOption |
P8248
|
FINISHED |
| Object | 16-valve DOHC head (on IROC R/T) |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 16-valve DOHC head (on IROC R/T) | Statement: [Dodge Daytona (K-derivative), valvetrainOption, 16-valve DOHC head (on IROC R/T)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valvetrainOption Context triple: [Dodge Daytona (K-derivative), valvetrainOption, 16-valve DOHC head (on IROC R/T)]
-
A.
valvetrainControl
Indicates a control relationship in which one entity regulates or manages the operation of an engine’s valvetrain system.
-
B.
valveGear
Indicates that one entity is the valve gear mechanism used to control the operation of another entity, typically an engine or similar machine.
-
C.
camshaftConfiguration
Indicates how the camshafts are arranged or configured within an engine’s valve train system.
-
D.
camshaftType
Indicates the specific design or configuration of camshaft associated with an engine or mechanical system.
-
E.
valvesPerCylinder
chosen
Indicates the number of valves associated with each individual cylinder in an engine.
- F. None of above.
Provenance (3 batches)
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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0a9b4481909477245d53f99cb0 |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:37 p.m.