Triple
T16627160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Lanarkshire Leisure and Culture |
E403979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cultural services provider |
C26443
|
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: Cultural services provider Context triple: [South Lanarkshire Leisure and Culture, instanceOf, Cultural services provider]
-
A.
leisure and entertainment company
A leisure and entertainment company is an organization that creates, manages, and delivers recreational, cultural, and amusement experiences to consumers through venues, events, media, or activities designed for enjoyment and relaxation.
-
B.
leisure services operator
chosen
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.
-
C.
cultural and entertainment company division
A cultural and entertainment company division is an organizational unit within a larger enterprise that develops, manages, and delivers cultural, artistic, and entertainment products or services to targeted audiences.
-
D.
cultural platform
A cultural platform is a digital or physical environment that curates, facilitates, and amplifies the creation, exchange, and preservation of cultural expressions, practices, and narratives among diverse communities.
-
E.
media and communications company
A media and communications company is an organization that creates, distributes, and manages content and messaging across various channels to inform, entertain, and connect audiences.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.