Triple
T4119602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annual Compliance Determination |
E90378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | oversight document |
C14761
|
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: oversight document Context triple: [Annual Compliance Determination, instanceOf, oversight document]
-
A.
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.
-
B.
administrative oversight regime
An administrative oversight regime is a structured system of rules, procedures, and institutions designed to monitor, review, and correct the actions and decisions of administrative bodies to ensure legality, accountability, and fairness.
-
C.
financial oversight office
A financial oversight office is an organizational unit responsible for monitoring, reviewing, and ensuring the accuracy, compliance, and integrity of an entity’s financial activities and reporting.
-
D.
intelligence oversight committee
An intelligence oversight committee is a formal body responsible for monitoring, reviewing, and regulating the activities of intelligence agencies to ensure legality, accountability, and alignment with democratic norms and national interests.
-
E.
police oversight body
A police oversight body is an independent or semi-independent organization responsible for monitoring, investigating, and reviewing police conduct to ensure accountability, transparency, and public trust in law enforcement.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:41 p.m.