Triple
T18727569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington’s 3rd judicial district |
E457944
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial district of Washington State |
C8808
|
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: judicial district of Washington State Context triple: [Washington’s 3rd judicial district, instanceOf, judicial district of Washington State]
-
A.
judicial district
chosen
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.
Oregon state court
An Oregon state court is a judicial body within the Oregon state court system that interprets and applies Oregon law to resolve civil, criminal, and administrative disputes arising under state jurisdiction.
-
C.
county in Washington State
A county in Washington State is an administrative and geographic subdivision of the state that provides local government services, governance, and regional organization for its constituent cities, towns, and unincorporated areas.
-
D.
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.
-
E.
region of Seattle
A region of Seattle represents a specific geographic area within the city, defined by boundaries and associated with particular neighborhoods, landmarks, and administrative or cultural characteristics.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.