Triple
T38313758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bal Mithai |
E1033767
|
entity |
| Predicate | hasCookingProcess |
P14777
|
FINISHED |
| Object | roasted khoya |
—
|
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: roasted khoya | Statement: [Bal Mithai, hasCookingProcess, roasted khoya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCookingProcess Context triple: [Bal Mithai, hasCookingProcess, roasted khoya]
-
A.
usesCookingMethod
chosen
Indicates that one entity prepares or processes another entity by applying a specific cooking technique or method.
-
B.
isCookedBy
Indicates that something has been prepared or made ready for eating through cooking by a particular agent.
-
C.
culinaryStatus
Indicates the current state or condition of something in relation to cooking or food preparation (e.g., raw, cooked, undercooked, burnt).
-
D.
typeOfPreparation
Indicates the method or process by which something is prepared or made ready for use, consumption, or further action.
-
E.
isUsuallyCookedIn
Indicates that something is most commonly or typically prepared or cooked within a particular container, appliance, or environment.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.