Triple
T21101061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfa Romeo Twin Cam inline-four |
E519904
|
entity |
| Predicate | camshaftDrive |
P83501
|
FINISHED |
| Object | double-row timing chain |
—
|
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: double-row timing chain | Statement: [Alfa Romeo Twin Cam inline-four, camshaftDrive, double-row timing chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: camshaftDrive Context triple: [Alfa Romeo Twin Cam inline-four, camshaftDrive, double-row timing chain]
-
A.
camshaftType
Indicates the specific design or configuration of camshaft associated with an engine or mechanical system.
-
B.
camshaftConfiguration
Indicates how the camshafts are arranged or configured within an engine’s valve train system.
-
C.
crankshaftType
Indicates the specific design or configuration of a crankshaft that an entity uses or is associated with.
-
D.
valvetrainControl
Indicates a control relationship in which one entity regulates or manages the operation of an engine’s valvetrain system.
-
E.
driveMechanism
chosen
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b5e16cc81908257ccf8c9a59117 |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.