Triple
T7389771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Student services of Humboldt University of Berlin |
E170469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | student services office |
C1291
|
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 services office Context triple: [Student services of Humboldt University of Berlin, instanceOf, student services office]
-
A.
student-life leadership office
The student-life leadership office is a campus unit that develops, supports, and coordinates programs, resources, and advising to foster student leadership, engagement, and community involvement.
-
B.
academic administrative office
chosen
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.
student
A student is an individual who actively engages in learning within an educational context, such as a school, university, or training program, to acquire knowledge, skills, and competencies.
-
D.
student section
A student section is a group of students enrolled together in the same course offering, typically sharing the same schedule, instructor, and classroom or online space.
-
E.
student life hub
A student life hub is a centralized platform or space that connects students to campus resources, events, organizations, and support services to enhance their overall academic and social experience.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:09 p.m.