Triple
T24211581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revelle Residence Life |
E600559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | student affairs unit |
C44414
|
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: student affairs unit Context triple: [Revelle Residence Life, instanceOf, student affairs unit]
-
A.
student affairs committee
A student affairs committee is a group responsible for overseeing, supporting, and improving students’ non-academic experiences, services, and well-being within an educational institution.
-
B.
university administrative unit
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.
student conduct office
The student conduct office is a university department responsible for investigating alleged student misconduct, enforcing institutional policies, and promoting a safe, respectful campus community through education and accountability processes.
-
D.
university organizational unit
chosen
A university organizational unit is a formally defined subdivision of a university—such as a college, school, department, or institute—responsible for managing specific academic, administrative, or research functions within the institution.
-
E.
student support service
A student support service is an institutional resource that provides academic, emotional, financial, and practical assistance to help students succeed and well-being throughout their educational journey.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 11:55 p.m.