Triple
T17655085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Informatics buildings |
E429599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university department building complex |
C21395
|
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 department building complex Context triple: [Department of Informatics buildings, instanceOf, university department building complex]
-
A.
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.
-
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.
institutional building complex
chosen
An institutional building complex is a coordinated group of structures and shared spaces designed to support the functions, services, and administration of an organization such as a university, hospital, or government entity.
-
D.
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.
-
E.
office building complex
An office building complex is a group of interconnected or closely situated office structures designed to provide workspace, shared amenities, and supporting services for multiple businesses or organizations.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 6:06 a.m.