Triple
T33768009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koenigsegg Agera S |
E865290
|
entity |
| Predicate | designedForFuelAvailability |
P197882
|
FINISHED |
| Object | markets without E85 biofuel |
—
|
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: markets without E85 biofuel | Statement: [Koenigsegg Agera S, designedForFuelAvailability, markets without E85 biofuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForFuelAvailability Context triple: [Koenigsegg Agera S, designedForFuelAvailability, markets without E85 biofuel]
-
A.
hasFuelStorage
Indicates that one entity possesses or is equipped with a facility, container, or system used to store fuel for later use.
-
B.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
C.
hasFuel
Indicates that an entity possesses or contains fuel available for use.
-
D.
fuelCondition
Indicates the state or quality of fuel associated with an entity, such as its level, usability, or readiness for operation.
-
E.
fuelLocation
Indicates the place or source where fuel is stored, supplied, or located for use.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
| PDg | Predicate description generation | batch_69feb5e50a7481908d6bff55bd85e06d |
completed | May 9, 2026, 4:19 a.m. |
Created at: May 1, 2026, 1:45 a.m.