Triple
T8193006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ANI Technologies Pvt. Ltd. |
E191359
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mobility company |
C2800
|
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: Mobility company Context triple: [ANI Technologies Pvt. Ltd., instanceOf, Mobility company]
-
A.
transportation services company
A transportation services company is an organization that plans, manages, and operates the movement of people or goods using various modes of transport, such as road, rail, air, or sea, often providing logistics, scheduling, and support services.
-
B.
transportation network company
chosen
A transportation network company is a business that uses digital platforms, typically mobile apps, to connect passengers with drivers who provide on-demand transportation services.
-
C.
transportation service
A transportation service is a system or business that moves people or goods from one location to another using various modes of transport under defined schedules, routes, and conditions.
-
D.
transport brand
A transport brand is a conceptual class representing a company or entity that provides transportation services or products, characterized by attributes like name, logo, service types, and reputation, and behaviors such as marketing, service delivery, and customer support.
-
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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:42 p.m.