Triple
T31561599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spotswood Recreation Department facilities |
E805280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public recreational facilities collection |
C22549
|
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 recreational facilities collection Context triple: [Spotswood Recreation Department facilities, instanceOf, public recreational facilities collection]
-
A.
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.
-
B.
recreational facility feature
A recreational facility feature is a specific physical or programmed element within a leisure-oriented environment designed to support, enhance, or enable recreational activities for users.
-
C.
public recreational area
A public recreational area is a shared outdoor or indoor space designed and maintained for community use, providing facilities and environments for leisure, exercise, social interaction, and relaxation.
-
D.
collection of parks
chosen
A collection of parks is an organized grouping of multiple park areas, managed or considered together as a unified set for recreation, conservation, or urban planning purposes.
-
E.
campus facility collection
A campus facility collection is an organized set of physical spaces, buildings, and infrastructure on an educational campus that together support academic, residential, recreational, and administrative activities.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:15 p.m.