Triple
T8821288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington superior courts |
E209907
|
entity |
| Predicate | hasJudicialOfficerType |
P10518
|
FINISHED |
| Object | superior court judge |
—
|
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: superior court judge | Statement: [Washington superior courts, hasJudicialOfficerType, superior court judge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJudicialOfficerType Context triple: [Washington superior courts, hasJudicialOfficerType, superior court judge]
-
A.
hasJudicialOfficer
Indicates that an entity is associated with or served by a specific judicial officer (such as a judge or magistrate) responsible for legal or court-related functions.
-
B.
hasJudgeType
chosen
Indicates that an entity is associated with a specific category or type of judge.
-
C.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
-
D.
isOfficerOf
Indicates that one entity holds an official position, role, or office within another entity (such as an organization, group, or institution).
-
E.
hasJuryType
Indicates that an entity is associated with, or classified by, a specific type or category of jury.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc601126248190b6f10c22f1aeac9a |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:46 p.m.