Triple
T17019219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landauer–Büttiker formalism |
E412901
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport theory |
C38655
|
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 theory Context triple: [Landauer–Büttiker formalism, instanceOf, transport theory]
-
A.
transport model
A transport model is a conceptual or mathematical representation used to simulate and analyze the movement of people, goods, or resources across a network or spatial system under various conditions and constraints.
-
B.
transport strategy
A transport strategy is a high-level plan that defines how people and goods will be moved efficiently, safely, sustainably, and cost-effectively within and between areas over a given time horizon.
-
C.
transport policy framework
A transport policy framework is a structured set of principles, goals, and regulatory tools that guide the planning, funding, operation, and governance of transportation systems to achieve economic, social, and environmental objectives.
-
D.
transportation research program
A transportation research program is an organized initiative that systematically studies and develops knowledge, technologies, and policies to improve the safety, efficiency, sustainability, and equity of transportation systems.
-
E.
public transport technology
Public transport technology encompasses the systems, vehicles, infrastructure, and digital tools used to plan, operate, and optimize shared transportation services such as buses, trains, trams, and metros.
- F. None of above. chosen
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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:33 a.m.