Triple
T13447631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court Executive Officer of the Marin County Superior Court |
E320524
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nonjudicial court leadership role |
C8184
|
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: nonjudicial court leadership role Context triple: [Court Executive Officer of the Marin County Superior Court, instanceOf, nonjudicial court leadership role]
-
A.
leadership role
A leadership role is a position in which an individual is responsible for guiding, influencing, and coordinating others to achieve shared goals and outcomes.
-
B.
judicial administrative office
chosen
A judicial administrative office is an organizational unit within the court system responsible for managing the non-judicial functions of the judiciary, such as case processing, records management, budgeting, staffing, and overall court operations support.
-
C.
quasi-judicial officer
A quasi-judicial officer is an individual or body authorized by law to conduct hearings, evaluate evidence, and make determinations or recommendations that resemble judicial decisions, but within an administrative or specialized regulatory context rather than a traditional court.
-
D.
judicial office
A judicial office is an official position within the judiciary in which an individual is authorized to interpret and apply the law, preside over legal proceedings, and issue binding decisions.
-
E.
court noble
A court noble is a high-ranking aristocrat who serves in close proximity to a monarch or royal household, often holding ceremonial, advisory, or administrative roles within the court.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:41 p.m.