Triple
T19487400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fireside Dinner Theatre |
E487547
|
entity |
| Predicate | typeOfFoodService |
P48322
|
FINISHED |
| Object | dinner service |
—
|
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: dinner service | Statement: [Fireside Dinner Theatre, typeOfFoodService, dinner service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFoodService Context triple: [Fireside Dinner Theatre, typeOfFoodService, dinner service]
-
A.
servesType
chosen
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
B.
foodCustom
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
C.
genreOfRecipes
Indicates that one entity is a genre or category that characterizes the type or style of recipes associated with another entity.
-
D.
cuisineType
Indicates the type or style of food associated with an entity, such as a restaurant or dish.
-
E.
feastType
Indicates the specific kind or category of feast associated with an event or occasion.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63441434081909bf26259bab677fe |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.