Triple

T9201633
Position Surface form Disambiguated ID Type / Status
Subject Glen Ellyn Park District E220853 entity
Predicate publicServiceDomain P66133 FINISHED
Object leisure services LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: leisure services | Statement: [Glen Ellyn Park District, publicServiceDomain, leisure services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publicServiceDomain
Context triple: [Glen Ellyn Park District, publicServiceDomain, leisure services]
  • A. publicDomain
    Indicates that a work or resource is not protected by intellectual property rights and is freely available for anyone to use, copy, modify, and distribute without restriction.
  • B. domainServed
    Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
  • C. publicServiceCategory chosen
    Indicates the classification or type of public service that an entity, activity, or offering belongs to.
  • D. inputDomain
    Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
  • E. defaultDomain
    Indicates that one entity serves as the standard or primary domain associated with another entity, used when no more specific domain is specified.
  • F. None of above.

Provenance (3 batches)

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_69ca83e8e9248190862cf3e41693b310 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd943cfb0819082231d80f0dc073b completed April 1, 2026, 8:37 a.m.
PD Predicate disambiguation batch_69cc660af2408190ae06eb8326e1c64e completed April 1, 2026, 12:25 a.m.
Created at: March 30, 2026, 7:25 p.m.