Triple
T35401994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davie County emergency services |
E1023258
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county emergency services agency |
C15381
|
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: county emergency services agency Context triple: [Davie County emergency services, instanceOf, county emergency services agency]
-
A.
county government agency
chosen
A county government agency is a local public organization responsible for administering specific services, regulations, and programs within a county’s jurisdiction on behalf of the county government.
-
B.
emergency services district
An emergency services district is a defined geographic area governed by a special-purpose local authority that organizes, funds, and oversees emergency response services such as fire protection, EMS, and rescue operations for the communities within its boundaries.
-
C.
county government facility
A county government facility is a building or complex where local county officials and departments conduct administrative, legislative, and public service functions for residents within the county’s jurisdiction.
-
D.
county government
A county government is a local administrative body responsible for providing regional services, enforcing laws, managing public resources, and implementing policies within a defined county jurisdiction.
-
E.
emergency management agency
An emergency management agency is an organization responsible for preparing for, coordinating, and responding to natural or human-made disasters to protect people, property, and the environment.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.