Triple
T29215391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | people flow solutions |
E740654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban mobility solution |
C29834
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: urban mobility solution Context triple: [people flow solutions, instanceOf, urban mobility solution]
-
A.
mobility services provider
A mobility services provider is an organization that offers and manages transportation solutions—such as ride-hailing, car-sharing, bike or scooter rentals, and integrated transit services—to enable people and goods to move efficiently from one place to another.
-
B.
urban transit technology
chosen
Urban transit technology encompasses the systems, vehicles, infrastructure, and digital tools that enable efficient, safe, and sustainable movement of people within cities.
-
C.
testbed for sustainable mobility
A testbed for sustainable mobility is a controlled, real-world or simulated environment where new transportation technologies, policies, and services are developed, integrated, and evaluated for their environmental, social, and economic impacts.
-
D.
transport technology company
A transport technology company develops and provides innovative digital solutions, platforms, and systems that optimize the planning, operation, and management of transportation services and infrastructure.
-
E.
micromobility device
A micromobility device is a small, lightweight, typically single-passenger vehicle—often electric-powered—designed for short-distance urban travel, such as e-scooters, e-bikes, and similar compact transport options.
- F. None of above.
Provenance (1 batch)
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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:13 p.m.