Triple
T30477576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAUR |
E775483
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | management authority |
C52546
|
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: management authority Context triple: [MAUR, instanceOf, management authority]
-
A.
administrative authority
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
-
B.
appointing authority
An appointing authority is an individual or entity legally empowered to select, hire, promote, or otherwise make official personnel decisions for positions within an organization or governmental body.
-
C.
management district
A management district is a designated geographic area within which a governing body coordinates and oversees specific services, regulations, and development activities to achieve targeted economic, environmental, or community objectives.
-
D.
managing agency
chosen
A managing agency is an organization or entity responsible for overseeing, coordinating, and administering the operations, resources, and strategic direction of a project, program, or group on behalf of its stakeholders or owners.
-
E.
management division
A management division is an organizational unit responsible for planning, directing, and coordinating resources and activities to achieve specific strategic and operational goals within a company or institution.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:12 p.m.