Triple
T32147330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | crème brûlée |
E821054
|
entity |
| Predicate | requiresKitchenTool |
P24520
|
FINISHED |
| Object | kitchen blowtorch |
—
|
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: kitchen blowtorch | Statement: [crème brûlée, requiresKitchenTool, kitchen blowtorch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresKitchenTool Context triple: [crème brûlée, requiresKitchenTool, kitchen blowtorch]
-
A.
isToolOf
chosen
Indicates that one entity functions as an instrument or means used by another entity to perform tasks or achieve goals.
-
B.
worksInKitchenAt
Indicates that an entity performs work or duties in the kitchen area of a specified location or organization.
-
C.
preparationRequirement
Indicates that one entity must be prepared, configured, or made ready as a necessary condition before another entity, action, or process can occur or be valid.
-
D.
requiresCookingTemperature
Indicates that performing the action or preparing the item necessitates reaching or maintaining a specific cooking temperature.
-
E.
eatenWithUtensil
Indicates that something was eaten using a specific utensil as the means of consumption.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 1, 2026, 12:31 a.m.