Triple
T8276856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Commissar for State Control of the RSFSR |
E193567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public oversight authority |
C17920
|
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: public oversight authority Context triple: [People's Commissar for State Control of the RSFSR, instanceOf, public oversight authority]
-
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.
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.
-
D.
federal oversight body
chosen
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.
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.
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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:51 p.m.