Triple
T38338242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strathclyde Fire and Rescue |
E1038020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former regional fire service |
C66397
|
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 service Context triple: [Strathclyde Fire and Rescue, instanceOf, former regional fire service]
-
A.
fire service pioneer
A fire service pioneer is an individual who introduces groundbreaking methods, technologies, or organizational practices that significantly advance the effectiveness, safety, and professionalism of firefighting and emergency response.
-
B.
firefighting organization
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.
-
C.
former organisation
chosen
A former organisation is an entity that previously existed and operated with a defined structure and purpose but has since been dissolved, merged, or otherwise ceased to function as an active organisation.
-
D.
fire chief
A fire chief is the highest-ranking officer in a fire department, responsible for overseeing all firefighting operations, personnel, training, safety protocols, and administrative functions to protect life and property.
-
E.
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.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.