Triple
T8570966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Criminal Court governance framework |
E202923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | oversight mechanism |
C5267
|
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 mechanism Context triple: [International Criminal Court governance framework, instanceOf, oversight mechanism]
-
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.
oversight document
An oversight document is a formal record that outlines monitoring activities, findings, and accountability measures to ensure compliance, performance, and proper governance within a process, project, or organization.
-
C.
monitoring mechanism
A monitoring mechanism is a system or process that continuously observes, measures, and evaluates activities or conditions to detect deviations, ensure compliance, and support timely decision-making.
-
D.
administrative oversight regime
chosen
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.
-
E.
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.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:21 p.m.