Triple
T27409225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 191st Street |
E692094
|
entity |
| Predicate | ADAAccess |
P23432
|
FINISHED |
| Object | elevator to street |
—
|
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: elevator to street | Statement: [191st Street, ADAAccess, elevator to street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ADAAccess Context triple: [191st Street, ADAAccess, elevator to street]
-
A.
wheelchairAccessibility
Indicates whether a place, service, or route is accessible and usable by people who use wheelchairs.
-
B.
accessible
Indicates that one entity can be reached, entered, used, or understood by another entity, often without undue difficulty or barriers.
-
C.
hasADAAccess
chosen
Indicates that an entity provides or is equipped with accessibility features compliant with the Americans with Disabilities Act (ADA), enabling access for people with disabilities.
-
D.
amenity
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
-
E.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd99324819099a95e2729e966e9 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:31 p.m.