Triple
T33392869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Division of Fire |
E855094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of the City of Cleveland government |
C11461
|
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: division of the City of Cleveland government Context triple: [Cleveland Division of Fire, instanceOf, division of the City of Cleveland government]
-
A.
division of a city attorney’s office
A division of a city attorney’s office is an organizational unit within the office that handles a specific category of legal responsibilities, such as civil litigation, criminal prosecution, advisory services, or municipal code enforcement.
-
B.
autonomous city government
An autonomous city government is a self-governing municipal authority that exercises significant political, administrative, and fiscal control over local affairs independent of higher levels of government.
-
C.
municipal agency
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.
-
D.
municipal organization
chosen
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
-
E.
district administration
District administration is the local governing and executive authority responsible for implementing government policies, managing public services, and coordinating development activities within a defined district.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.