Triple
T35752082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus F1 Team |
E1033344
|
entity |
| Predicate | fuelAndLubricantsSupplier |
P51152
|
FINISHED |
| Object | Total |
E555210
|
NE 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: Total | Statement: [Lotus F1 Team, fuelAndLubricantsSupplier, Total]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelAndLubricantsSupplier Context triple: [Lotus F1 Team, fuelAndLubricantsSupplier, Total]
-
A.
fuelSupplier
chosen
Indicates that one entity supplies fuel to another as a provider in a fuel-related relationship.
-
B.
hasFuelServices
Indicates that one entity provides or is equipped with fuel-related services or facilities for another entity.
-
C.
oilSystem
Indicates a relationship where an entity functions as, is part of, or is associated with an oil-based system used for lubrication, operation, or processing.
-
D.
hasRefuelingSystemSupplier
Indicates that one entity serves as the supplier or provider of the refueling system for another entity.
-
E.
oilType
Indicates the specific kind or classification of oil associated with an entity.
- F. None of above.
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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a197aee48190bbd69f670a3f7721 |
completed | May 3, 2026, 7:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3885f5117c8190a80efcb1df0685fc |
completed | June 22, 2026, 12:46 a.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.