Triple
T8481534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Health Plan |
E200530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state health insurance program |
C17375
|
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: state health insurance program Context triple: [Oregon Health Plan, instanceOf, state health insurance program]
-
A.
state-level disability advocacy program
A state-level disability advocacy program is a coordinated initiative, typically funded or sanctioned by state government, that provides support, representation, and systemic advocacy to protect and advance the rights, access, and inclusion of people with disabilities within that state.
-
B.
health insurance exchange
A health insurance exchange is a marketplace, typically organized by a government or authorized entity, where individuals and small businesses can compare, purchase, and enroll in standardized health insurance plans.
-
C.
state government
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
-
D.
health insurance provider
chosen
A health insurance provider is an organization that offers and manages health coverage plans, collecting premiums and paying for or reimbursing members’ eligible medical expenses according to policy terms.
-
E.
state system
A state system is a structured framework in which distinct political entities (states) interact under shared norms, rules, and institutions that regulate their behavior and relationships.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:12 p.m.