Triple
T22541860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilberforce University Alumni Multiplex |
E557310
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-purpose campus facility |
C12924
|
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: multi-purpose campus facility Context triple: [Wilberforce University Alumni Multiplex, instanceOf, multi-purpose campus facility]
-
A.
multi-purpose facility
chosen
A multi-purpose facility is a versatile building or space designed to support a wide range of activities, events, and functions through adaptable layouts and shared resources.
-
B.
university campus building
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.
-
C.
multi-campus university
A multi-campus university is an institution of higher education that operates multiple geographically separate campuses under a single administrative and academic governance structure.
-
D.
campus facility collection
A campus facility collection is an organized set of physical spaces, buildings, and infrastructure on an educational campus that together support academic, residential, recreational, and administrative activities.
-
E.
multi-purpose event venue
A multi-purpose event venue is a flexible space designed to accommodate a wide range of gatherings—such as conferences, concerts, weddings, and exhibitions—by offering adaptable layouts, technical infrastructure, and support services.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:51 p.m.