Triple
T28391247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maricopa County Attorney’s Office |
E719160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county attorney’s office |
C3125
|
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: county attorney’s office Context triple: [Maricopa County Attorney’s Office, instanceOf, county attorney’s office]
-
A.
county district attorney office
chosen
The county district attorney office is a government legal agency responsible for prosecuting criminal cases on behalf of the public within a specific county jurisdiction.
-
B.
county counsel office
A county counsel office is a governmental legal department that provides civil legal advice, representation, and services to a county’s governing body, departments, and agencies.
-
C.
county sheriff's office
A county sheriff's office is a local law enforcement agency responsible for maintaining public safety, enforcing laws, operating jails, serving legal documents, and providing court security within a specific county jurisdiction.
-
D.
county government legal position
A county government legal position is a role within a county’s public administration responsible for providing legal advice, drafting and reviewing legal documents, ensuring compliance with laws and regulations, and representing the county in legal proceedings.
-
E.
court office
A court office is an administrative unit within a judicial system responsible for managing case records, scheduling hearings, processing legal documents, and supporting the day-to-day operations of 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:13 a.m.