Triple
T24120123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molson Park |
E597629
|
entity |
| Predicate | hasRecreationalAmenities |
P6792
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Molson Park, hasRecreationalAmenities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalAmenities Context triple: [Molson Park, hasRecreationalAmenities, yes]
-
A.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
B.
hasRecreationFacility
chosen
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
-
C.
hasRecreationalUseNearby
Indicates that there is at least one location or facility for recreational activities situated close to the referenced entity.
-
D.
hasRegionalAmenity
Indicates that a region provides or contains a specific amenity or facility within its area.
-
E.
hasRecreationalOrganization
Indicates that an entity is associated with, or hosts, a recreational organization such as a club, team, or leisure group.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee2defc81909df55900769fef5b |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:05 p.m.