Triple
T13123833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Case Management/Electronic Case Files |
E311793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal judiciary information system |
C14105
|
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 information system Context triple: [Case Management/Electronic Case Files, instanceOf, federal judiciary information system]
-
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.
judicial network
chosen
A judicial network is a structured system of interconnected courts, judges, and legal institutions that interact through case decisions, precedents, and administrative relationships to shape and apply the law.
-
C.
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.
-
D.
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.
-
E.
federal jurisdiction case
A federal jurisdiction case is a legal dispute that is heard in a federal court because it involves federal laws, the U.S. Constitution, the federal government, or parties from different states meeting specific jurisdictional requirements.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:07 p.m.