Triple
T38303475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Parks swimming pool system |
E1032283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal recreation facility network |
C49858
|
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: municipal recreation facility network Context triple: [New York City Parks swimming pool system, instanceOf, municipal recreation facility network]
-
A.
recreational facility system
chosen
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.
recreation area network
A recreation area network is an interconnected system of parks, open spaces, and recreational facilities designed to provide accessible leisure, sports, and outdoor experiences across a region.
-
C.
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.
-
D.
municipal services network
A municipal services network is an integrated system of interconnected public infrastructure, agencies, and digital platforms that coordinate to deliver essential city services such as water, waste management, transportation, and emergency response to residents and businesses.
-
E.
sports and recreation facility
A sports and recreation facility is a place designed and equipped for individuals or groups to engage in physical activities, sports, exercise, and leisure pursuits.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.