Triple
T699733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Supreme Court as an enforcement of the Thirteenth Amendment |
E13971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal court function |
C269
|
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: federal court function Context triple: [United States Supreme Court as an enforcement of the Thirteenth Amendment, instanceOf, federal court function]
-
A.
federal court
chosen
A federal court is a judicial body established by a national government with authority to hear and decide cases arising under that nation’s constitution, federal laws, and treaties.
-
B.
federal district
A federal district is a distinct territorial unit under the direct jurisdiction of a national government, separate from any constituent state or province, typically established to house the nation's capital or serve special administrative purposes.
-
C.
federal government
The federal government is the central governing authority of a nation that holds supreme power over national affairs, such as defense, foreign policy, and regulation of interstate matters, while sharing sovereignty with regional or state governments.
-
D.
court of law
A court of law is an official institution where legal disputes are heard, evidence is evaluated, and binding judgments are made according to established laws and procedures.
-
E.
judiciary
The judiciary is the branch of government responsible for interpreting laws, resolving disputes, and ensuring justice is administered fairly and in accordance with the constitution and legal principles.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:36 p.m.