Triple
T30618840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knox County government offices |
E779387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government building complex |
C21395
|
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: local government building complex Context triple: [Knox County government offices, instanceOf, local government building complex]
-
A.
civic building complex
A civic building complex is a coordinated group of public structures and spaces designed to house governmental, administrative, and community services within a unified physical setting.
-
B.
institutional building complex
chosen
An institutional building complex is a coordinated group of structures and shared spaces designed to support the functions, services, and administration of an organization such as a university, hospital, or government entity.
-
C.
government building
A government building is a structure owned or used by a public authority to house offices, services, and functions related to the administration and governance of a city, region, or country.
-
D.
vicinity of government building
The vicinity of a government building is the surrounding area, including streets, sidewalks, and public spaces, that lies in close physical proximity to the government facility and is often subject to heightened security and regulatory measures.
-
E.
state government complex
A state government complex is a centralized group of buildings and facilities where a state's executive, legislative, and often judicial branches conduct official governmental operations and public services.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:26 p.m.