Triple
T22195474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary-General to ensure adequate resources for the United Nations Office of Counter-Terrorism |
E548535
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative responsibility |
C11864
|
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 responsibility Context triple: [Secretary-General to ensure adequate resources for the United Nations Office of Counter-Terrorism, instanceOf, administrative responsibility]
-
A.
administrative obligation
An administrative obligation is a duty imposed on individuals or organizations to complete specific formal procedures, filings, or compliance tasks required by governing authorities or institutional rules.
-
B.
administrative authority
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
-
C.
administrative function
chosen
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.
-
D.
administrative instrument
An administrative instrument is a formal tool, document, or mechanism used by an organization or authority to implement, manage, or regulate administrative processes and decisions.
-
E.
administrative section
An administrative section is a defined organizational unit within an institution or system responsible for managing specific administrative tasks, processes, or services.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:35 p.m.