Triple
T28990907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari V6 turbo hybrid |
E736022
|
entity |
| Predicate | governingFuelLimit |
P109354
|
FINISHED |
| Object | FIA race fuel mass limit |
—
|
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: FIA race fuel mass limit | Statement: [Ferrari V6 turbo hybrid, governingFuelLimit, FIA race fuel mass limit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingFuelLimit Context triple: [Ferrari V6 turbo hybrid, governingFuelLimit, FIA race fuel mass limit]
-
A.
fuelFlowLimit
chosen
Indicates a constraint on the maximum allowable rate at which fuel can flow in a system or component.
-
B.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
-
C.
hasEnergyDeploymentLimitPerLap
Indicates that there is a maximum amount of energy that may be deployed or used per lap in a given context or system.
-
D.
governingSpeedRange
Indicates the range of speeds within which a governing or limiting mechanism is intended to operate or apply.
-
E.
fuelTypeLicensed
Indicates that an entity is authorized or licensed to use, supply, or handle a specified type of fuel.
- 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_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: April 28, 2026, 9:25 a.m.