Triple
T8740419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Chancellery of Switzerland |
E207485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | staff office |
C9619
|
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: staff office Context triple: [Federal Chancellery of Switzerland, instanceOf, staff office]
-
A.
private office
A private office is an enclosed workspace designated for an individual or small group, providing privacy, reduced noise, and a controlled environment for focused work and confidential activities.
-
B.
public office
A public office is an official position of authority and responsibility within a government or public institution, held to serve the interests and welfare of the public under established laws and regulations.
-
C.
clerical office
A clerical office is a workplace where administrative tasks such as record-keeping, correspondence, data entry, and document management are performed to support an organization’s operations.
-
D.
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.
-
E.
bureau-level office
chosen
A bureau-level office is an organizational unit within a larger department or agency that operates at the bureau tier, managing specialized programs, policies, or services under that bureau’s authority.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:38 p.m.