Triple
T25044566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thom cobordism theory |
E627198
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cobordism theory |
C22356
|
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: cobordism theory Context triple: [Thom cobordism theory, instanceOf, cobordism theory]
-
A.
theory in differential topology
A theory in differential topology is a coherent framework of concepts, theorems, and techniques that studies the properties of smooth manifolds and smooth maps between them that are invariant under smooth deformations.
-
B.
cohomology theory
chosen
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.
-
C.
result in low-dimensional topology
A result in low-dimensional topology is a theorem or proposition that characterizes the structure, classification, or properties of topological spaces and manifolds of dimension four or less.
-
D.
work in geometric topology
Work in geometric topology studies the properties and structures of spaces that are preserved under continuous deformations, focusing on the interplay between geometry and topology in shapes and manifolds.
-
E.
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.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:08 a.m.