Triple
T27916448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Diablo restaurant |
E706086
|
entity |
| Predicate | fuelUsage |
P22119
|
FINISHED |
| Object | does not use conventional fuel for main grill |
—
|
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: does not use conventional fuel for main grill | Statement: [El Diablo restaurant, fuelUsage, does not use conventional fuel for main grill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelUsage Context triple: [El Diablo restaurant, fuelUsage, does not use conventional fuel for main grill]
-
A.
fuelConsumption
Indicates the amount of fuel used by an entity (such as a vehicle or device) over a specified distance, time, or operation.
-
B.
oilUsage
Indicates the amount or pattern of oil consumed or utilized by an entity over a given context or period.
-
C.
fuelEfficiency
Indicates how effectively an entity uses fuel to perform a given amount of work or travel a certain distance.
-
D.
fuelTransport
Indicates the transfer or conveyance of fuel from one location or entity to another.
-
E.
typicalFuel
chosen
Indicates the kind of fuel that is normally or most commonly used by an entity (such as a device, vehicle, or system).
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:54 p.m.