Triple
T9989889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia initially refused to comply with the Supreme Court’s decision |
E196858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | states’ rights controversy |
C9175
|
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: states’ rights controversy Context triple: [Georgia initially refused to comply with the Supreme Court’s decision, instanceOf, states’ rights controversy]
-
A.
constitutional debate
A constitutional debate is a structured discussion in which participants argue differing interpretations, applications, or proposed changes to a constitution’s principles and provisions.
-
B.
compromise over slavery
A compromise over slavery is a negotiated political agreement that temporarily balances conflicting pro- and anti-slavery interests, typically by making concessions on the expansion, regulation, or recognition of slavery to preserve broader union or stability.
-
C.
public policy controversy
chosen
A public policy controversy is a sustained, often polarized dispute among stakeholders over the goals, design, implementation, or consequences of government actions or regulations.
-
D.
controversy
Controversy is a state of public disagreement or heated debate arising from conflicting opinions, values, or interpretations about a particular issue, event, or decision.
-
E.
Reconstruction-era legislation
Reconstruction-era legislation comprises the post–Civil War laws and constitutional amendments enacted between 1865 and 1877 to abolish slavery, define citizenship, protect civil rights, and restructure political power in the former Confederate states.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:50 p.m.