Triple
T31352060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GE Trivection oven |
E799621
|
entity |
| Predicate | hasCookingMode |
P56153
|
FINISHED |
| Object | thermal bake |
—
|
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: thermal bake | Statement: [GE Trivection oven, hasCookingMode, thermal bake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCookingMode Context triple: [GE Trivection oven, hasCookingMode, thermal bake]
-
A.
cookingAppliance
Indicates that one entity is an appliance used by another entity for cooking food.
-
B.
hasCookingQuality
Indicates that something possesses a particular characteristic or attribute related to cooking, such as flavor, texture, or suitability for a cooking method.
-
C.
heatingMethod
chosen
Indicates the method or technique used to apply heat to something, such as for cooking, warming, or processing.
-
D.
usesCookingMethod
Indicates that one entity prepares or processes another entity by applying a specific cooking technique or method.
-
E.
requiresCookingTemperature
Indicates that performing the action or preparing the item necessitates reaching or maintaining a specific cooking temperature.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0207a1272c81909dcdb6e3307702f5 |
completed | May 11, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a0205fa1e608190829fd2baa0434fff |
completed | May 11, 2026, 4:38 p.m. |
Created at: April 29, 2026, 9:17 p.m.