Triple
T36605297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Be Our Guest Restaurant |
E903028
|
entity |
| Predicate | previouslyServedMeal |
P200654
|
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: [Be Our Guest Restaurant, previouslyServedMeal, breakfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyServedMeal Context triple: [Be Our Guest Restaurant, previouslyServedMeal, breakfast]
-
A.
servedBefore
Indicates that one entity was served prior to another in time or sequence.
-
B.
lastMeal
Indicates the most recent meal consumed by an entity in time.
-
C.
servedDuring
Indicates that one entity held a role, position, or performed a function within the time period defined by another entity.
-
D.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
E.
servedTogetherWith
Indicates that two entities were provided, offered, or used at the same time as part of the same service, event, or context.
- F. None of above. chosen
Provenance (4 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69ff9d9ba1ac8190a0cca5764bb5904d |
completed | May 9, 2026, 8:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.