Triple
T26440875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander polynomial |
E665082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Laurent polynomial-valued invariant |
C51573
|
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: Laurent polynomial-valued invariant Context triple: [Alexander polynomial, instanceOf, Laurent polynomial-valued invariant]
-
A.
3-manifold invariant
A 3-manifold invariant is a quantity or structure assigned to a 3-dimensional manifold that remains unchanged under homeomorphisms or diffeomorphisms, used to distinguish and classify such manifolds.
-
B.
quantum invariant
A quantum invariant is a quantity associated with a quantum system or topological object that remains unchanged under specified transformations, often used to distinguish or classify quantum states, knots, or manifolds.
-
C.
object in invariant theory
An object in invariant theory is a mathematical entity, such as a vector space, polynomial ring, or group action, whose structure and symmetries are studied through the functions or quantities that remain unchanged under a specified group of transformations.
-
D.
homological invariant
A homological invariant is a quantity or structure derived from homology theory that remains unchanged under specified transformations, used to distinguish and classify mathematical objects up to an appropriate notion of equivalence.
-
E.
problem in invariant theory
A problem in invariant theory concerns determining and characterizing the algebraic functions (invariants) that remain unchanged under the action of a given group on a vector space or algebraic variety.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:58 p.m.