Triple
T21537612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Promenade Ontario |
E531388
|
entity |
| Predicate | pedestrianFeatures |
P144145
|
FINISHED |
| Object | wide sidewalks |
—
|
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: wide sidewalks | Statement: [Promenade Ontario, pedestrianFeatures, wide sidewalks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pedestrianFeatures Context triple: [Promenade Ontario, pedestrianFeatures, wide sidewalks]
-
A.
pedestrianFriendly
Indicates that an environment, route, or area is designed or suitable for safe, comfortable, and convenient use by pedestrians.
-
B.
pedestrianActivity
Indicates that an entity is engaged in or associated with walking or other on-foot movement or behavior.
-
C.
pedestrianRole
Indicates that an entity participates in a situation specifically in the role of a pedestrian, i.e., a person traveling on foot.
-
D.
pedestrianizedAreas
Indicates areas where vehicle traffic is restricted or removed so that pedestrians have priority use of the space.
-
E.
pedestrianOrientation
Indicates the directional facing or heading of a pedestrian relative to a reference frame or environment.
- F. None of above. chosen
Provenance (4 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0fdf448190b47ac7c28904f86b |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:27 p.m.