Triple
T25617633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Table Table |
E642200
|
entity |
| Predicate | typicalMealPeriod |
P46097
|
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: [Table Table, typicalMealPeriod, breakfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMealPeriod Context triple: [Table Table, typicalMealPeriod, breakfast]
-
A.
mealPeriod
chosen
Indicates the time-of-day category (such as breakfast, lunch, or dinner) during which a meal or food-related event occurs.
-
B.
typicalMealStructure
Indicates the usual sequence and composition of courses or components that make up a standard meal.
-
C.
commonMealType
Indicates that two entities share the same general category or type of meal (e.g., breakfast, lunch, dinner).
-
D.
typicallyEatenAt
Indicates that something is most commonly or customarily eaten during a particular time, event, or context.
-
E.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 21, 2026, 5:01 p.m.