Triple
T15519704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dillard University Office of Church and Community Relations |
E368927
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | campus office |
C10705
|
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: campus office Context triple: [Dillard University Office of Church and Community Relations, instanceOf, campus office]
-
A.
campus
A campus is a defined area of land that houses the buildings, facilities, and open spaces of an educational institution, supporting academic, residential, and social activities.
-
B.
academic administrative office
An academic administrative office is a centralized unit within an educational institution responsible for managing academic records, coordinating course and program logistics, supporting faculty and students with administrative processes, and ensuring compliance with institutional and regulatory policies.
-
C.
government campus
A government campus is a designated area comprising multiple buildings and facilities where various governmental departments and agencies are co-located to conduct administrative, legislative, or public service functions.
-
D.
campus axis
A campus axis is a primary organizing line or pathway that structures the spatial layout, circulation, and visual relationships of buildings and open spaces across a campus.
-
E.
university campus building
chosen
A university campus building is a physical structure within a university’s grounds designed to support academic, administrative, residential, or recreational functions for students, faculty, and staff.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 4:04 a.m.