Triple
T25124657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyss |
E629363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport administrator |
C25226
|
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: public transport administrator Context triple: [Skyss, instanceOf, public transport administrator]
-
A.
transportation executive
A transportation executive is a senior leader responsible for planning, directing, and optimizing an organization’s transportation and logistics operations to ensure efficient, cost-effective, and compliant movement of goods or people.
-
B.
transport entrepreneur
A transport entrepreneur is an individual who identifies, develops, and manages innovative business opportunities in the movement of people or goods, leveraging logistics, technology, and market insights to create efficient and profitable transportation solutions.
-
C.
transportation organization
A transportation organization is an entity that plans, manages, and operates systems or services that move people or goods from one location to another.
-
D.
transit official
chosen
A transit official is a public authority responsible for planning, regulating, and overseeing the safe, efficient, and reliable operation of transportation systems and services.
-
E.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:28 a.m.