Triple
T31886281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holden Forests & Gardens |
E814014
|
entity |
| Predicate | hasPublicGreenSpaces |
P45219
|
FINISHED |
| Object | urban gardens |
—
|
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: urban gardens | Statement: [Holden Forests & Gardens, hasPublicGreenSpaces, urban gardens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicGreenSpaces Context triple: [Holden Forests & Gardens, hasPublicGreenSpaces, urban gardens]
-
A.
hasGreenSpaces
chosen
Indicates that an entity includes or is associated with areas of vegetation or natural greenery, such as parks, gardens, or lawns.
-
B.
hasNearbyGreenSpace
Indicates that an entity is located close to an area of green space, such as a park, garden, or natural vegetation.
-
C.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
D.
isGreenSpaceFor
Indicates that one entity serves as a designated green or open space intended for use or benefit by another entity.
-
E.
isUrbanOpenSpace
Indicates that a given area functions as an open, publicly accessible space within an urban environment.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 30, 2026, 11:57 p.m.