Triple
T29274250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randomized evaluations of health insurance expansions |
E742206
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | policy evaluation study |
C32316
|
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: policy evaluation study Context triple: [Randomized evaluations of health insurance expansions, instanceOf, policy evaluation study]
-
A.
policy research program
A policy research program is an organized initiative that systematically investigates public issues, evaluates policy options, and generates evidence-based recommendations to inform decision-making and improve governance outcomes.
-
B.
policy research project
chosen
A policy research project is a structured, systematic investigation designed to analyze public issues, evaluate existing or proposed policies, and generate evidence-based recommendations for decision-makers.
-
C.
policy bureau
A policy bureau is an organizational unit within a government or institution responsible for researching, developing, coordinating, and overseeing the implementation of policies in a specific domain.
-
D.
policy analysis unit
A policy analysis unit is an organizational entity responsible for systematically evaluating, comparing, and forecasting the impacts of public or institutional policies to inform evidence-based decision-making.
-
E.
policy report
A policy report is a structured document that analyzes a specific issue, evaluates options, and presents evidence-based recommendations to guide decision-making by policymakers or stakeholders.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:50 p.m.