Triple
T21647849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ful medames |
E534263
|
entity |
| Predicate | commonMealTime |
P53136
|
FINISHED |
| Object | morning |
—
|
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: morning | Statement: [ful medames, commonMealTime, morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonMealTime Context triple: [ful medames, commonMealTime, morning]
-
A.
commonMealType
Indicates that two entities share the same general category or type of meal (e.g., breakfast, lunch, dinner).
-
B.
typicallyEatenAt
chosen
Indicates that something is most commonly or customarily eaten during a particular time, event, or context.
-
C.
mealPeriod
Indicates the time-of-day category (such as breakfast, lunch, or dinner) during which a meal or food-related event occurs.
-
D.
typicalMealStructure
Indicates the usual sequence and composition of courses or components that make up a standard meal.
-
E.
mealStandard
Indicates that something conforms to a defined or expected standard for a meal (e.g., quality, composition, or requirements).
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59124e1c81908d454894d66359e7 |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.