Triple
T7929871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Emergency Board |
E184161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | budgetary oversight body |
C1876
|
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: budgetary oversight body Context triple: [Oregon Emergency Board, instanceOf, budgetary oversight body]
-
A.
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.
-
B.
financial oversight office
chosen
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.
-
C.
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.
-
D.
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.
-
E.
space agency oversight body
A space agency oversight body is an authoritative organization responsible for monitoring, evaluating, and guiding a space agency’s policies, programs, safety, and compliance to ensure accountability, effectiveness, and alignment with national or international objectives.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:07 p.m.