Triple
T11420571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twin Cam engine |
E270605
|
entity |
| Predicate | boreStrokeType |
P87198
|
FINISHED |
| Object | long-stroke V-twin |
—
|
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: long-stroke V-twin | Statement: [Twin Cam engine, boreStrokeType, long-stroke V-twin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boreStrokeType Context triple: [Twin Cam engine, boreStrokeType, long-stroke V-twin]
-
A.
boreStrokeDesign
chosen
Indicates that an engine’s bore and stroke configuration is designed or specified in a particular way.
-
B.
hasBoreType
Indicates that an entity is characterized by or associated with a specific type of bore (e.g., cylindrical, tapered, rifled).
-
C.
cylinderBore
Indicates the diameter of the cylindrical chamber (bore) in which a piston or similar component moves.
-
D.
crankshaftType
Indicates the specific design or configuration of a crankshaft that an entity uses or is associated with.
-
E.
boreSpacing
Indicates the center-to-center distance between adjacent bores or holes in a component or assembly.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b20ce08190befc98379b879985 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.