Triple
T16563262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT Facilities |
E402392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university facilities 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 facilities department Context triple: [MIT Facilities, instanceOf, university facilities department]
-
A.
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.
-
B.
university administration building
A university administration building is a central facility on campus that houses offices and services responsible for managing the institution’s academic, financial, and operational affairs.
-
C.
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.
-
D.
university system headquarters
The university system headquarters is the central administrative entity that oversees, coordinates, and supports the policies, operations, and strategic direction of all institutions within a multi-campus university system.
-
E.
university wellness center
A university wellness center is a campus facility that provides integrated physical, mental, and preventive health services, programs, and resources to support students’ overall well-being and academic success.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:15 a.m.