Triple
T32973655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradise Garden Grill |
E843593
|
entity |
| Predicate | hasMenuCharacteristic |
P197913
|
FINISHED |
| Object | limited-time offerings |
—
|
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: limited-time offerings | Statement: [Paradise Garden Grill, hasMenuCharacteristic, limited-time offerings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMenuCharacteristic Context triple: [Paradise Garden Grill, hasMenuCharacteristic, limited-time offerings]
-
A.
hasMenuItem
Indicates that one entity (typically a menu or menu section) includes or offers another entity as one of its menu items.
-
B.
hasFictionalMenuItemFeature
Indicates that a fictional menu item possesses a particular characteristic, attribute, or feature.
-
C.
hasMenuBoard
Indicates that one entity provides or is equipped with a menu board associated with another entity.
-
D.
hasMenuRange
Indicates that an entity offers items or services within a specified range or scope on its menu.
-
E.
hasTastingMenu
Indicates that an establishment offers a predefined multi-course tasting menu as part of its dining options.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
| PDg | Predicate description generation | batch_69feb8e6ed7881908446745c89c30784 |
completed | May 9, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:22 a.m.