Triple
T36076304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M189 |
E1043503
|
entity |
| Predicate | typicalFuelRequirement |
P22119
|
FINISHED |
| Object | high-octane petrol |
—
|
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: high-octane petrol | Statement: [M189, typicalFuelRequirement, high-octane petrol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFuelRequirement Context triple: [M189, typicalFuelRequirement, high-octane petrol]
-
A.
typicalFuel
chosen
Indicates the kind of fuel that is normally or most commonly used by an entity (such as a device, vehicle, or system).
-
B.
requiresFuel
Indicates that an entity depends on some form of fuel in order to operate or perform its function.
-
C.
fuelConsumption
Indicates the amount of fuel used by an entity (such as a vehicle or device) over a specified distance, time, or operation.
-
D.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
E.
fleetFuelType
Indicates the type of fuel used by a fleet as a whole or by vehicles within that fleet.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.