Triple
T35405749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contact Center CoE |
E1023359
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Organizational Unit |
C64206
|
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: Organizational Unit Context triple: [Contact Center CoE, instanceOf, Organizational Unit]
-
A.
organizational unit category
An organizational unit category is a classification that groups organizational units based on shared characteristics such as function, structure, or hierarchy to support consistent management and analysis.
-
B.
organizational unit designation
An organizational unit designation is a label or identifier that specifies a distinct division, department, or functional group within an organization’s structure.
-
C.
Verwaltungseinheit
Eine Verwaltungseinheit ist eine organisatorische Einheit innerhalb einer öffentlichen oder privaten Institution, die für die Erfüllung bestimmter Verwaltungsaufgaben und die Umsetzung von Richtlinien in einem abgegrenzten Zuständigkeitsbereich verantwortlich ist.
-
D.
university organizational unit
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.
former organisational unit
A former organisational unit is an administrative or structural division within an organization that previously existed but has since been dissolved, merged, or restructured and no longer functions in its original form.
- F. None of above. chosen
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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.