Triple
T11909555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Pick |
E283357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport administrator |
C8930
|
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: transport administrator Context triple: [Frank Pick, instanceOf, transport administrator]
-
A.
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.
-
B.
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.
-
C.
transportation executive
chosen
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.
-
D.
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.
-
E.
transport ministry
The transport ministry is a government department responsible for planning, regulating, and overseeing a nation’s transportation systems and infrastructure, including roads, railways, air, and maritime transport.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.