Triple
T2742103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western District of Washington |
E60773
|
entity |
| Predicate | hasDistrictJudges |
P16419
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: yes | Statement: [Western District of Washington, hasDistrictJudges, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistrictJudges Context triple: [Western District of Washington, hasDistrictJudges, yes]
-
A.
hasJudicialDistrict
Indicates that an entity falls within or is associated with a specific judicial district for legal or court-related purposes.
-
B.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
C.
hasCountyJudge
Indicates that a specified jurisdiction or administrative area is served or overseen by a particular county judge.
-
D.
authorizedJudgeships
chosen
Indicates the number or set of judicial positions that are officially established and permitted by law or authority for a given court or jurisdiction.
-
E.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
- F. None of above.
Provenance (3 batches)
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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb303898819098a7d192e29817f8 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.