Triple
T33054055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yule log |
E845802
|
entity |
| Predicate | culinaryForm |
P175752
|
FINISHED |
| Object | sponge cake roll |
—
|
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: sponge cake roll | Statement: [Yule log, culinaryForm, sponge cake roll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culinaryForm Context triple: [Yule log, culinaryForm, sponge cake roll]
-
A.
culinaryStatus
Indicates the current state or condition of something in relation to cooking or food preparation (e.g., raw, cooked, undercooked, burnt).
-
B.
recipe
Indicates that one entity is a set of instructions or method used to create, prepare, or produce another entity.
-
C.
foodPreparationStyle
Indicates the manner or method by which food is prepared, cooked, or processed.
-
D.
genreOfRecipes
Indicates that one entity is a genre or category that characterizes the type or style of recipes associated with another entity.
-
E.
culinaryUse
Indicates that one entity is used in the preparation, flavoring, or serving of food or drink for another entity.
- F. None of above. chosen
Provenance (4 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:24 a.m.