Triple
T12527972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch cuisine |
E299486
|
entity |
| Predicate | commonMealStructure |
P26228
|
FINISHED |
| Object | simple breakfast |
—
|
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: simple breakfast | Statement: [Dutch cuisine, commonMealStructure, simple breakfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonMealStructure Context triple: [Dutch cuisine, commonMealStructure, simple breakfast]
-
A.
typicalMealStructure
chosen
Indicates the usual sequence and composition of courses or components that make up a standard meal.
-
B.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
-
C.
typicallyEatenAt
Indicates that something is most commonly or customarily eaten during a particular time, event, or context.
-
D.
hasMealType
Indicates that an entity is associated with a specific category or type of meal (such as breakfast, lunch, or dinner).
-
E.
dietaryOptions
Indicates the types of diets or food-related preferences, restrictions, or choices that are applicable to or offered for an entity.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.