Triple
T8557046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverside Drive |
E202596
|
entity |
| Predicate | hasPublicSpaceAccess |
P62705
|
FINISHED |
| Object | Riverside Park entrances |
—
|
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: Riverside Park entrances | Statement: [Riverside Drive, hasPublicSpaceAccess, Riverside Park entrances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicSpaceAccess Context triple: [Riverside Drive, hasPublicSpaceAccess, Riverside Park entrances]
-
A.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
B.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
C.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
D.
hasParkAccess
chosen
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
E.
isInPublicSpace
Indicates that an entity is located within a space that is publicly accessible or open to the general public.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe946d1408190adc7dfb7b2173f9d |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.