Triple
T33629828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seiberg–Witten invariants |
E861521
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | smooth 4-manifold invariant |
C27157
|
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: smooth 4-manifold invariant Context triple: [Seiberg–Witten invariants, instanceOf, smooth 4-manifold 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.
Laurent polynomial-valued invariant
A Laurent polynomial-valued invariant is a quantity assigned to mathematical objects (such as knots, links, or manifolds) that remains unchanged under specified transformations and takes the form of a Laurent polynomial in one or more variables.
-
C.
homological invariant
chosen
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.
-
D.
four-dimensional manifold
A four-dimensional manifold is a topological space that locally resembles four-dimensional Euclidean space, meaning each point has a neighborhood homeomorphic to an open subset of ℝ⁴.
-
E.
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.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.