Triple
T24179228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School of Tourism and Hotel Management |
E599369
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hospitality and tourism 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: hospitality and tourism school Context triple: [School of Tourism and Hotel Management, instanceOf, hospitality and tourism school]
-
A.
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.
-
B.
hospitality training program
A hospitality training program is a structured course designed to develop the customer service, operational, and interpersonal skills required for professional roles in the hospitality industry.
-
C.
hospitality service
A hospitality service is a business or offering that provides lodging, food, beverages, and related amenities to guests, focusing on comfort, convenience, and positive customer experiences.
-
D.
hospitality industry event
A hospitality industry event is a planned gathering where professionals from hotels, restaurants, travel, and related services meet to network, showcase offerings, share industry insights, and explore business opportunities.
-
E.
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.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:34 p.m.