Triple
T11359611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Week in Review (local versions and specials) |
E269050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public affairs program |
C30047
|
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 affairs program Context triple: [Washington Week in Review (local versions and specials), instanceOf, public affairs program]
-
A.
domestic policy program
A domestic policy program is a coordinated set of government actions and initiatives designed to address specific national issues and objectives within a country’s borders.
-
B.
policy program
A policy program is a coordinated set of government or organizational initiatives, actions, and resources designed to achieve specific public or institutional goals through the implementation of formal policies.
-
C.
program of a state government agency
A program of a state government agency is an organized set of activities, services, and resources designed and managed by the agency to achieve specific public policy goals or deliver particular benefits to residents within the state.
-
D.
political project
A political project is a coordinated set of ideas, goals, and actions aimed at transforming or preserving power relations, institutions, or public policies within a political community.
-
E.
nonprofit organization program
A nonprofit organization program is a structured set of coordinated activities and services designed and operated by a nonprofit to advance its mission and create specific social, cultural, or environmental impact for a defined target population.
- F. None of above. chosen
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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:33 p.m.