Triple
T12072557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Support for the Civil Rights Act reauthorizations |
E287459
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public policy stance |
C29938
|
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 policy stance Context triple: [Support for the Civil Rights Act reauthorizations, instanceOf, public policy stance]
-
A.
public policy doctrine
A public policy doctrine is a legal principle that allows courts or governments to limit, invalidate, or shape actions, contracts, or decisions that conflict with the broader interests, values, or welfare of society.
-
B.
public policy controversy
A public policy controversy is a sustained, often polarized dispute among stakeholders over the goals, design, implementation, or consequences of government actions or regulations.
-
C.
public policy mechanism
A public policy mechanism is a structured tool, process, or instrument used by governments or public institutions to influence behavior, allocate resources, or achieve specific societal outcomes.
-
D.
public policy domain
The public policy domain encompasses the processes, institutions, and frameworks through which governments and stakeholders identify societal issues, design and implement policy solutions, and evaluate their impacts on the public.
-
E.
public policy office
A public policy office is an organizational unit within a government or institution responsible for researching, developing, analyzing, and coordinating policies to address public issues and guide decision-making.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:48 p.m.