Triple
T27133845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontryagin duality |
E681628
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mathematical duality theory |
C28303
|
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: mathematical duality theory Context triple: [Pontryagin duality, instanceOf, mathematical duality theory]
-
A.
duality theory
chosen
Duality theory is a conceptual framework in mathematics and related fields that studies pairs of structures or problems that are interrelated in such a way that results and properties in one can be systematically translated into corresponding results and properties in the other.
-
B.
electric–magnetic duality
Electric–magnetic duality is a symmetry in certain physical theories that interchanges electric and magnetic fields or charges, often mapping a strongly coupled description of a system to a weakly coupled one while preserving its physical content.
-
C.
mathematical program
A mathematical program is an optimization model that seeks to minimize or maximize an objective function subject to a set of mathematical constraints.
-
D.
result in convex analysis
In convex analysis, a result is a formally stated and proven fact—such as a theorem, lemma, or proposition—that characterizes properties or relationships of convex sets, convex functions, or related optimization structures.
-
E.
mathematical structure
A mathematical structure is a set (or collection of objects) equipped with specified operations, relations, or properties that satisfy given axioms, providing a framework for studying abstract patterns and relationships.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:06 a.m.