Triple
T24806533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander duality |
E620671
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | topological duality theorem |
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: topological duality theorem Context triple: [Alexander duality, instanceOf, topological duality theorem]
-
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.
topological algebra
A topological algebra is an algebra over a field that is also a topological vector space, where the algebraic operations (addition, scalar multiplication, and multiplication) are continuous with respect to the topology.
-
C.
topology
Topology is the mathematical study of properties of spaces that are preserved under continuous deformations such as stretching or bending, but not tearing or gluing.
-
D.
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.
-
E.
cohomology theory
A cohomology theory is a functorial assignment of graded algebraic invariants to topological spaces (or other mathematical objects) that encodes global structural and obstruction information via axioms such as exactness and homotopy invariance.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:50 a.m.