Triple
T5412843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary |
E121052
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative profession |
C7558
|
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: administrative profession Context triple: [Secretary, instanceOf, administrative profession]
-
A.
public administration position
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
-
B.
administrative function
An administrative function is a conceptual class representing tasks and processes that support the organization, coordination, and control of operations within an institution or system.
-
C.
administrative category
An administrative category is a classification used by organizations or governments to group entities, activities, or data for the purposes of management, regulation, and record-keeping.
-
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.
professional occupation
chosen
A professional occupation is a specialized role in the workforce that requires advanced knowledge, formal training or credentials, and adherence to established standards or ethics to provide expert services in a particular field.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:05 p.m.