Triple
T28990906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari V6 turbo hybrid |
E736022
|
entity |
| Predicate | governingFuelFlowLimit |
P109354
|
FINISHED |
| Object | FIA fuel flow regulations |
—
|
NE NERFINISHED |
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: FIA fuel flow regulations | Statement: [Ferrari V6 turbo hybrid, governingFuelFlowLimit, FIA fuel flow regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingFuelFlowLimit Context triple: [Ferrari V6 turbo hybrid, governingFuelFlowLimit, FIA fuel flow regulations]
-
A.
fuelFlowLimit
chosen
Indicates a constraint on the maximum allowable rate at which fuel can flow in a system or component.
-
B.
fuelControl
Indicates a relationship where one entity regulates, manages, or influences the supply or use of fuel for another entity or system.
-
C.
fuelMeteringMethod
Indicates how fuel is measured, controlled, or delivered within a system or process.
-
D.
fuelTypeRegulated
Indicates that the type of fuel used by an entity is subject to specific rules, standards, or regulatory controls.
-
E.
fuelManagement
Indicates the management, control, or optimization of fuel usage, storage, and distribution within a system or process.
- 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_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: April 28, 2026, 9:25 a.m.