Triple
T25892931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School of Hospitality, Food and Tourism Management |
E652384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | foodservice management school |
C13451
|
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: foodservice management school Context triple: [School of Hospitality, Food and Tourism Management, instanceOf, foodservice management school]
-
A.
culinary school
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.
food service business
A food service business is an organization that prepares, sells, and/or serves food and beverages to customers for on- or off-premise consumption.
-
C.
hospitality school
chosen
A hospitality school is an educational institution that provides specialized training and academic programs in areas such as hotel management, tourism, culinary arts, and event planning to prepare students for careers in the hospitality industry.
-
D.
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.
-
E.
foodservice industry event
A foodservice industry event is a planned gathering where professionals and stakeholders in the food and beverage sector meet to network, showcase products, share knowledge, and explore business opportunities.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:22 a.m.