Triple
T13308737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Bankruptcy Court for the District of South Dakota |
E317005
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States bankruptcy 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 bankruptcy court Context triple: [United States Bankruptcy Court for the District of South Dakota, instanceOf, United States bankruptcy court]
-
A.
bankruptcy trustee
A bankruptcy trustee is a court-appointed fiduciary responsible for administering a debtor’s bankruptcy estate, liquidating or managing assets, and distributing proceeds fairly to creditors in accordance with bankruptcy law.
-
B.
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.
-
C.
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.
-
D.
court-appointed trustee
A court-appointed trustee is a neutral third party designated by a court to manage, protect, and administer assets or affairs on behalf of beneficiaries or creditors in accordance with legal and fiduciary duties.
-
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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:29 p.m.