Triple
T17153773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States bankruptcy courts in the Northern District of Georgia |
E416288
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal 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: federal bankruptcy court Context triple: [United States bankruptcy courts in the Northern District of Georgia, instanceOf, federal bankruptcy 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.
bankruptcy chapter
A bankruptcy chapter is a specific section of bankruptcy law that outlines the rules, procedures, and eligibility requirements for a particular type of debt relief or reorganization case.
-
C.
bankruptcy law case
A bankruptcy law case is a legal proceeding in which a court resolves issues related to an individual’s or entity’s inability to repay debts, including asset liquidation, debt reorganization, and creditor claims.
-
D.
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.
-
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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:37 a.m.