Triple
T22696201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Public Works of the District of Columbia |
E561179
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public works authority |
C14004
|
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: public works authority Context triple: [Board of Public Works of the District of Columbia, instanceOf, public works authority]
-
A.
administrative authority
chosen
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.
public works ministry
A public works ministry is a government department responsible for planning, developing, and maintaining public infrastructure and services such as roads, bridges, water systems, and public buildings.
-
C.
occupation authority section
An occupation authority section is a designated part of a document or system that defines, records, and manages the official powers, responsibilities, and permissions associated with a specific job or role.
-
D.
occupation authority office
An occupation authority office is an administrative body established by a foreign power to govern, regulate, and oversee civil, legal, and economic affairs in a territory under military or political occupation.
-
E.
occupation authority component
An occupation authority component is a system element responsible for defining, managing, and enforcing rules, permissions, and responsibilities associated with specific roles or professions within an organizational or regulatory context.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:14 p.m.