Triple
T18889434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagel |
E462042
|
entity |
| Predicate | requiresCookingMethod |
P14777
|
FINISHED |
| Object | Boiling in water or lye solution |
—
|
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: Boiling in water or lye solution | Statement: [Bagel, requiresCookingMethod, Boiling in water or lye solution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCookingMethod Context triple: [Bagel, requiresCookingMethod, Boiling in water or lye solution]
-
A.
usesCookingMethod
chosen
Indicates that one entity prepares or processes another entity by applying a specific cooking technique or method.
-
B.
requiresCookingTemperature
Indicates that performing the action or preparing the item necessitates reaching or maintaining a specific cooking temperature.
-
C.
isCookedBy
Indicates that something has been prepared or made ready for eating through cooking by a particular agent.
-
D.
isUsuallyCookedIn
Indicates that something is most commonly or typically prepared or cooked within a particular container, appliance, or environment.
-
E.
heatingMethod
Indicates the method or technique used to apply heat to something, such as for cooking, warming, or processing.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c479f3208190a9d665865c4b630b |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.