Triple
T4020076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Circuit Court for the Eastern District of Pennsylvania |
E91258
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States circuit court |
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: United States circuit court Context triple: [United States Circuit Court for the Eastern District of Pennsylvania, instanceOf, United States circuit court]
-
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.
judicial district
A judicial district is a defined geographic area within which a particular court or set of courts has legal authority to hear and decide cases.
-
C.
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.
-
D.
United States state court case
A United States state court case is a legal dispute adjudicated within a state’s judicial system, governed by that state’s laws and procedures rather than federal law.
-
E.
component of the United States Court of Federal Claims
A component of the United States Court of Federal Claims is an organizational unit or functional division within the court that supports its judicial mission, such as through case management, administration, or specialized legal services.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:35 p.m.