Triple
T12379941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT Dining |
E295719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university dining services department |
C1500
|
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: university dining services department Context triple: [MIT Dining, instanceOf, university dining services department]
-
A.
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.
-
B.
university administrative unit
chosen
A university administrative unit is an organizational division within a university responsible for managing specific operational, academic, or support functions to ensure the institution runs effectively and complies with policies and regulations.
-
C.
university dormitory
A university dormitory is a residential building on or near a campus that provides students with shared or individual living spaces and basic amenities during their studies.
-
D.
university museum service
A university museum service manages the curation, preservation, interpretation, and public presentation of collections to support the institution’s educational, research, and community engagement missions.
-
E.
university centre
A university centre is a dedicated facility or organizational unit within a university that provides specialized services, resources, or programs to support academic, research, or student-focused activities.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:54 p.m.