Triple
T27715196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor ham |
E698796
|
entity |
| Predicate | typicalMeal |
P110353
|
FINISHED |
| Object | 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: breakfast | Statement: [Taylor ham, typicalMeal, breakfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMeal Context triple: [Taylor ham, typicalMeal, breakfast]
-
A.
commonMealType
chosen
Indicates that two entities share the same general category or type of meal (e.g., breakfast, lunch, dinner).
-
B.
intendedMeal
Indicates that one entity is the meal that another entity plans or expects to eat.
-
C.
mealStandard
Indicates that something conforms to a defined or expected standard for a meal (e.g., quality, composition, or requirements).
-
D.
typicalMealStructure
Indicates the usual sequence and composition of courses or components that make up a standard meal.
-
E.
intendedFood
Indicates that one entity is the food item that another entity plans or is meant to eat or consume.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
Created at: April 27, 2026, 3:04 p.m.