Triple
T28990914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari V6 turbo hybrid |
E736022
|
entity |
| Predicate | governingCylinderConfiguration |
P132348
|
FINISHED |
| Object | V6 only |
—
|
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: V6 only | Statement: [Ferrari V6 turbo hybrid, governingCylinderConfiguration, V6 only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingCylinderConfiguration Context triple: [Ferrari V6 turbo hybrid, governingCylinderConfiguration, V6 only]
-
A.
pistonConfiguration
chosen
Indicates the specific arrangement and layout of pistons within an engine or mechanical system.
-
B.
numberOfCylinders
Indicates the count of engine cylinders associated with an entity.
-
C.
boreStrokeConfiguration
Indicates a relationship where an engine’s bore and stroke dimensions are specified or configured relative to a particular design or component.
-
D.
camshaftConfiguration
Indicates how the camshafts are arranged or configured within an engine’s valve train system.
-
E.
cylinderHeads
Indicates a relationship where one entity serves as a cylinder head (or set of cylinder heads) for another, typically as a component in an engine or mechanical 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: April 28, 2026, 9:25 a.m.