Triple
T23086391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3.0-liter twin-turbocharged V6 Nettuno |
E575614
|
entity |
| Predicate | fuelInjection |
P142180
|
FINISHED |
| Object | direct injection |
—
|
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: direct injection | Statement: [3.0-liter twin-turbocharged V6 Nettuno, fuelInjection, direct injection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelInjection Context triple: [3.0-liter twin-turbocharged V6 Nettuno, fuelInjection, direct injection]
-
A.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
B.
fuelEnrichment
Indicates the degree to which a fuel has been processed to increase the concentration of its active or fissile component relative to its natural state.
-
C.
refuellingSystem
Indicates a system or mechanism used to supply fuel from one entity to another.
-
D.
fuelSystemFeature
chosen
Indicates that there is a specific characteristic, component, or functional aspect associated with a fuel system.
-
E.
fuelControl
Indicates a relationship where one entity regulates, manages, or influences the supply or use of fuel for another entity or 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da652ac819085919ade6dd7bce4 |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.