Triple
T11118557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook’s Meadow Loop Trail |
E262958
|
entity |
| Predicate | wheelchairAccessibility |
P97044
|
FINISHED |
| Object | partially accessible |
—
|
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: partially accessible | Statement: [Cook’s Meadow Loop Trail, wheelchairAccessibility, partially accessible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelchairAccessibility Context triple: [Cook’s Meadow Loop Trail, wheelchairAccessibility, partially accessible]
-
A.
usesWheelchair
Indicates that an entity relies on or operates a wheelchair for mobility or transportation.
-
B.
hasWheelchairSpace
Indicates that an object, location, or vehicle includes designated space that can accommodate a wheelchair user.
-
C.
wheelchairTransferRequired
Indicates that a person must be transferred into or out of a wheelchair in order to perform or complete the associated activity or service.
-
D.
hasWheelchairLanes
Indicates that a location, route, or facility includes designated lanes or pathways specifically designed for wheelchair use.
-
E.
wheelchairEventsIncluded
Indicates that the specified events explicitly include or accommodate the use of wheelchairs.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79af6fe448190b042c2e77b855b05 |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750cb26f48190a134614d0aa8e283 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:28 p.m.