Triple
T36605305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Be Our Guest Restaurant |
E903028
|
entity |
| Predicate | previousServiceModel |
P200674
|
FINISHED |
| Object | quick-service for 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: quick-service for breakfast | Statement: [Be Our Guest Restaurant, previousServiceModel, quick-service for breakfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousServiceModel Context triple: [Be Our Guest Restaurant, previousServiceModel, quick-service for breakfast]
-
A.
previousServiceType
Indicates that one service type directly preceded another in a sequence or history of services.
-
B.
previousServiceBranch
Indicates that an entity was formerly associated with or served in a specified service branch before its current one.
-
C.
hasFormerService
Indicates that an entity previously provided a service to another entity but no longer does so.
-
D.
predecessorModel
Indicates that one model directly precedes another in a sequence, version history, or developmental lineage.
-
E.
priorService
Indicates that one entity has previously provided service or served in a role, position, or capacity before the current context or event.
- 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_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69ff9e90b5248190bdd8d13f966b63e1 |
completed | May 9, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:11 p.m.