Triple
T35762166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumfries and Galloway Fire and Rescue Service |
E1033905
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former regional fire and rescue authority |
C8085
|
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: former regional fire and rescue authority Context triple: [Dumfries and Galloway Fire and Rescue Service, instanceOf, former regional fire and rescue authority]
-
A.
firefighting organization
chosen
A firefighting organization is a coordinated group responsible for preventing, controlling, and extinguishing fires, as well as responding to related emergencies to protect life, property, and the environment.
-
B.
former local municipality
A former local municipality is an administrative area that once had its own local government authority but has since been dissolved, merged, or restructured into a different governing entity.
-
C.
regional heritage authority
A regional heritage authority is an organization responsible for identifying, protecting, managing, and promoting cultural and historical assets within a specific geographic region.
-
D.
former seat of local government
A former seat of local government is a building or location that previously served as the primary administrative center for a local governing authority but no longer holds that official function.
-
E.
former municipal government
A former municipal government is a previously existing local governing body or administrative authority that has been dissolved, merged, or replaced and no longer exercises official jurisdiction over its former municipality.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.