Triple
T35752645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Formula One season |
E1033355
|
entity |
| Predicate | fuelSupplierRegulation |
P51152
|
FINISHED |
| Object | single fuel supplier per team |
—
|
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: single fuel supplier per team | Statement: [2017 Formula One season, fuelSupplierRegulation, single fuel supplier per team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelSupplierRegulation Context triple: [2017 Formula One season, fuelSupplierRegulation, single fuel supplier per team]
-
A.
fuelTypeRegulated
Indicates that the type of fuel used by an entity is subject to specific rules, standards, or regulatory controls.
-
B.
fuelSupplier
chosen
Indicates that one entity supplies fuel to another as a provider in a fuel-related relationship.
-
C.
fuelTypeLicensed
Indicates that an entity is authorized or licensed to use, supply, or handle a specified type of fuel.
-
D.
fuelTransport
Indicates the transfer or conveyance of fuel from one location or entity to another.
-
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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.