Triple
T659768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Internal Oversight Services |
E11727
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal audit body |
C3533
|
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: internal audit body Context triple: [Office of Internal Oversight Services, instanceOf, internal audit body]
-
A.
auditing institution
chosen
An auditing institution is an independent organization responsible for systematically examining and evaluating financial records, operations, and controls to ensure accuracy, compliance, and accountability.
-
B.
advisory body
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
-
C.
independent administrative authority
An independent administrative authority is a public body, separate from the traditional executive hierarchy, endowed with regulatory or supervisory powers and functional autonomy to ensure impartial decision-making in a specific sector or policy area.
-
D.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
E.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.