Triple
T24892923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 35th Judicial District Court of Louisiana |
E623053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Louisiana district court |
C47703
|
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: Louisiana district court Context triple: [35th Judicial District Court of Louisiana, instanceOf, Louisiana district court]
-
A.
Louisiana state court
chosen
A Louisiana state court is a judicial body within the Louisiana state court system that interprets and applies Louisiana law to resolve civil, criminal, family, and other legal disputes arising under its jurisdiction.
-
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.
former district of Louisiana Territory
A former district of Louisiana Territory is an obsolete administrative subdivision that once functioned as a regional governing unit within the historical U.S. Louisiana Territory before being reorganized into new territorial or state jurisdictions.
-
E.
parish of Louisiana
A parish of Louisiana is a primary local government and administrative division in the state, equivalent to a county in other U.S. states, responsible for regional governance, services, and law enforcement.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:26 a.m.