Triple
T1689203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia Office of Zoning |
E36512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | zoning authority |
C825
|
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: zoning authority Context triple: [District of Columbia Office of Zoning, instanceOf, zoning authority]
-
A.
occupation authority division
Occupation authority division is the organizational structure and allocation of powers among governing bodies or agencies responsible for administering and controlling a territory under military or foreign occupation.
-
B.
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.
-
C.
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.
-
D.
stadium authority
A stadium authority is an organization, typically public or quasi-public, responsible for owning, managing, financing, and overseeing the operation and development of a sports or entertainment stadium and its surrounding facilities.
-
E.
municipal agency
chosen
A municipal agency is a local government organization responsible for delivering specific public services, enforcing local regulations, and managing community programs within a city or town.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:29 p.m.