Triple
T28051033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esaki–Tsu relation |
E708819
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport theory relation |
C13348
|
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 relation Context triple: [Esaki–Tsu relation, instanceOf, transport theory relation]
-
A.
transport theory
Transport theory is the conceptual framework that describes how particles, energy, or quantities such as mass and charge move and are distributed within physical systems under the influence of processes like diffusion, convection, and external forces.
-
B.
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.
-
C.
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.
-
D.
dispersion relation
A dispersion relation is a mathematical expression that links the frequency of a wave to its wavenumber (or energy to momentum), describing how different wavelengths propagate through a medium or system.
-
E.
constitutive relation
chosen
A constitutive relation is a mathematical or physical law that links field variables (such as stress and strain or electric field and polarization) to characterize how a specific material or medium responds to external influences.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:33 p.m.