Triple
T11092244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TMB 7000 series |
E262283
|
entity |
| Predicate | hasWheelchairAccessibility |
P70033
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TMB 7000 series, hasWheelchairAccessibility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWheelchairAccessibility Context triple: [TMB 7000 series, hasWheelchairAccessibility, yes]
-
A.
hasWheelchairSpace
chosen
Indicates that an object, location, or vehicle includes designated space that can accommodate a wheelchair user.
-
B.
usesWheelchair
Indicates that an entity relies on or operates a wheelchair for mobility or transportation.
-
C.
isWheelchairAccessibleInPart
Indicates that an entity is only partially accessible to wheelchair users, with some but not all areas or features meeting accessibility requirements.
-
D.
hasWheelchairLanes
Indicates that a location, route, or facility includes designated lanes or pathways specifically designed for wheelchair use.
-
E.
hasStepFreeAccess
Indicates that a location, facility, or route can be accessed without using stairs, typically via ramps, lifts, or level entrances.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799ec6564819097624195d0cd9093 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.