Triple
T28990912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari V6 turbo hybrid |
E736022
|
entity |
| Predicate | fuelManagement |
P166091
|
FINISHED |
| Object | electronic engine management system |
—
|
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: electronic engine management system | Statement: [Ferrari V6 turbo hybrid, fuelManagement, electronic engine management system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelManagement Context triple: [Ferrari V6 turbo hybrid, fuelManagement, electronic engine management system]
-
A.
fuelTransport
Indicates the transfer or conveyance of fuel from one location or entity to another.
-
B.
fuelCondition
Indicates the state or quality of fuel associated with an entity, such as its level, usability, or readiness for operation.
-
C.
fuelFraction
Indicates the proportion of an object's total mass or capacity that consists of fuel.
-
D.
fuelConsumption
Indicates the amount of fuel used by an entity (such as a vehicle or device) over a specified distance, time, or operation.
-
E.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
- F. None of above. chosen
Provenance (4 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_69f65f7d3b5c8190937aaddff2879989 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 9:25 a.m.