Triple
T23493180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cityrunner Graz type |
E571630
|
entity |
| Predicate | lowFloorAccessibility |
P97044
|
FINISHED |
| Object | wheelchair 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: wheelchair accessible | Statement: [Cityrunner Graz type, lowFloorAccessibility, wheelchair accessible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowFloorAccessibility Context triple: [Cityrunner Graz type, lowFloorAccessibility, wheelchair accessible]
-
A.
lowFloor
Indicates that something has a floor positioned close to ground level, allowing easy, step-free access.
-
B.
hasLowerFloor
Indicates that one location, structure, or level includes or is directly connected to a floor situated below another floor.
-
C.
hasStepFreeAccess
Indicates that a location, facility, or route can be accessed without using stairs, typically via ramps, lifts, or level entrances.
-
D.
floorAccess
Indicates that an entity is permitted to enter or use a specific floor or level within a building or structure.
-
E.
wheelchairAccessibility
chosen
Indicates whether a place, service, or route is accessible and usable by people who use wheelchairs.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dd56408190b459077e433ed1c3 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.