Triple
T34238209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pebbles |
E878389
|
entity |
| Predicate | typicalMealContext |
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: [Pebbles, typicalMealContext, breakfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMealContext Context triple: [Pebbles, typicalMealContext, breakfast]
-
A.
commonMealType
chosen
Indicates that two entities share the same general category or type of meal (e.g., breakfast, lunch, dinner).
-
B.
typicalMealStructure
Indicates the usual sequence and composition of courses or components that make up a standard meal.
-
C.
intendedMeal
Indicates that one entity is the meal that another entity plans or expects to eat.
-
D.
mealStandard
Indicates that something conforms to a defined or expected standard for a meal (e.g., quality, composition, or requirements).
-
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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.