Triple
T30159698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medway Council leisure services network |
E766627
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public leisure services system |
C23643
|
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: public leisure services system Context triple: [Medway Council leisure services network, instanceOf, public leisure services system]
-
A.
leisure services operator
A leisure services operator manages and coordinates recreational facilities, programs, and activities to provide enjoyable, safe, and accessible leisure experiences for clients or the public.
-
B.
recreational facility system
A recreational facility system is an integrated framework of spaces, equipment, services, and management processes designed to support and coordinate leisure, fitness, and community activities for users.
-
C.
public service facility
A public service facility is a place or infrastructure provided by government or community organizations to deliver essential services such as health, safety, education, or administration to the public.
-
D.
public emergency service system
A public emergency service system is an integrated network of agencies, communication channels, and response resources that coordinates rapid assistance and protection for the public during crises, disasters, and urgent incidents.
-
E.
public service system
chosen
A public service system is an organized framework of institutions, processes, and resources designed to deliver essential services and support to the public in an efficient, equitable, and transparent manner.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:21 p.m.