Triple
T8747686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapelfield |
E207872
|
entity |
| Predicate | hasLeisureType |
P3451
|
FINISHED |
| Object | family-oriented leisure facilities |
—
|
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: family-oriented leisure facilities | Statement: [Chapelfield, hasLeisureType, family-oriented leisure facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeisureType Context triple: [Chapelfield, hasLeisureType, family-oriented leisure facilities]
-
A.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
B.
isRecreationalArea
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
-
C.
hasRecreationType
chosen
Indicates that an entity is associated with or offers a particular type or category of recreational activity.
-
D.
hasRecreationalOrganization
Indicates that an entity is associated with, or hosts, a recreational organization such as a club, team, or leisure group.
-
E.
hasRecreationPurpose
Indicates that something is used or intended to be used for recreational or leisure activities.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da2d67c819094b2b39c78384d0d |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.