Triple
T11647770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ex parte Merryman |
E276818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Civil War legal case |
C29580
|
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: American Civil War legal case Context triple: [Ex parte Merryman, instanceOf, American Civil War legal case]
-
A.
American Civil War document
An American Civil War document is any written, printed, or official record created during or about the U.S. Civil War (1861–1865) that provides evidence of military, political, social, or personal aspects of the conflict.
-
B.
United States slavery case
A United States slavery case is a legal dispute, historical or contemporary, that addresses the status, treatment, or legacy of enslaved persons within the jurisdiction of U.S. law.
-
C.
fugitive slave law case
A fugitive slave law case is a legal proceeding arising from the capture, return, or status of an escaped enslaved person under statutes mandating the recovery of individuals fleeing enslavement.
-
D.
civil rights era case
A civil rights era case is a legal dispute, typically from the mid-20th century United States, that addresses issues of racial segregation, discrimination, or the protection and expansion of civil liberties and equal rights under the law.
-
E.
colonial legal case
A colonial legal case is a formal dispute or prosecution adjudicated within a legal system established by a colonial power over a subject territory, reflecting the laws, institutions, and power dynamics of colonial rule.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.