Triple
T36257774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idaho Avenue NW |
E891989
|
entity |
| Predicate | hasNearbyParkOrGreenSpace |
P33602
|
FINISHED |
| Object | Glover-Archbold Park area |
—
|
NE NERFINISHED |
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: Glover-Archbold Park area | Statement: [Idaho Avenue NW, hasNearbyParkOrGreenSpace, Glover-Archbold Park area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyParkOrGreenSpace Context triple: [Idaho Avenue NW, hasNearbyParkOrGreenSpace, Glover-Archbold Park area]
-
A.
hasNearbyGreenSpace
chosen
Indicates that an entity is located close to an area of green space, such as a park, garden, or natural vegetation.
-
B.
hasNearbyParkFeature
Indicates that one place or object is located close to a park-related feature, such as a park, playground, or green space.
-
C.
hasNearbyParkEntrance
Indicates that one location is situated close to an entrance of a park.
-
D.
isNeighborhoodParkOf
Indicates that a park is located within and serves as a local recreational area for a specific neighborhood.
-
E.
hasNearbyProvincialPark
Indicates that one entity is located close to, or in the vicinity of, a provincial park.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a004fd3caf48190b2ec063a7bf0756b |
completed | May 10, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a004f7672dc8190aca91d1ed855bf9a |
completed | May 10, 2026, 9:27 a.m. |
Created at: May 3, 2026, 4:09 p.m.