Triple
T16277330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judicial branch of the United States government |
E395166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal judiciary |
C830
|
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 judiciary Context triple: [Judicial branch of the United States government, instanceOf, federal judiciary]
-
A.
federal court
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.
judiciary
chosen
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.
-
C.
component of the federal judiciary
A component of the federal judiciary is an institutional unit—such as a court, office, or administrative body—that performs specific judicial or support functions within the structure of the national court system.
-
D.
federal judiciary role
A federal judiciary role is a position within the national court system responsible for interpreting and applying federal law, resolving disputes under its jurisdiction, and upholding constitutional principles.
-
E.
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.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:05 a.m.