Triple
T7912267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superior Court of the District of Columbia |
E183727
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States territorial-style court |
C23168
|
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 territorial-style court Context triple: [Superior Court of the District of Columbia, instanceOf, United States territorial-style court]
-
A.
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.
-
B.
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.
-
C.
regional court
A regional court is a judicial body with authority to hear and decide legal cases within a specific geographic area below the national level.
-
D.
United States territorial entity
A United States territorial entity is a geographically defined area under the jurisdiction or sovereignty of the United States, including states, territories, districts, and other dependent areas, recognized for legal, political, or administrative purposes.
-
E.
federal territory
A federal territory is a geographic area under the direct jurisdiction and administration of a federal government, distinct from constituent states or provinces and typically lacking the same degree of self-governance.
- F. None of above. chosen
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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:04 p.m.