Triple
T26798206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jungers Culinary Center |
E671022
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | culinary school facility |
C557
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: culinary school facility Context triple: [Jungers Culinary Center, instanceOf, culinary school facility]
-
A.
culinary school
chosen
A culinary school is an educational institution where students learn cooking techniques, food preparation, kitchen management, and related culinary arts to become professional chefs or food industry specialists.
-
B.
culinary school network
A culinary school network is an organized group of affiliated culinary institutions that share resources, standards, curricula, and industry partnerships to provide coordinated culinary education and training across multiple locations.
-
C.
royal culinary facility
A royal culinary facility is a specialized kitchen complex within a palace or royal estate where highly trained staff prepare, store, and manage food and beverages for the royal household and official state functions.
-
D.
on-campus dining venue
An on-campus dining venue is a food service location situated within a college or university that provides meals, snacks, and beverages to students, faculty, staff, and visitors, often accepting campus meal plans and offering spaces for socializing or studying.
-
E.
culinary department
The culinary department is an organizational unit responsible for planning, preparing, and overseeing all food production and kitchen operations within a hospitality or food service establishment.
- F. None of above.
Provenance (1 batch)
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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 4:21 a.m.