Triple
T22262409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Auditor |
E550261
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government oversight role |
C46023
|
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: government oversight role Context triple: [Public Auditor, instanceOf, government oversight role]
-
A.
government oversight agency
A government oversight agency is an official body responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards within public or private sector activities to ensure accountability and integrity.
-
B.
oversight authority
An oversight authority is an independent body or designated entity responsible for monitoring, reviewing, and ensuring that organizations or processes comply with established laws, regulations, standards, and ethical norms.
-
C.
government agency oversight body
A government agency oversight body is an independent or semi-independent entity responsible for monitoring, evaluating, and ensuring that government agencies operate legally, ethically, efficiently, and in alignment with established policies and public interests.
-
D.
federal oversight body
A federal oversight body is a government entity responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards across federal agencies or sectors to ensure accountability and integrity.
-
E.
oversight mandate
An oversight mandate is an authoritative directive that assigns responsibility to monitor, review, and ensure compliance or accountability within a specific domain, process, or organization.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:39 p.m.