Triple
T25073640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontryagin classes |
E627990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | characteristic classes |
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: characteristic classes Context triple: [Pontryagin classes, instanceOf, characteristic classes]
-
A.
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.
-
B.
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.
-
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.
classical invariant
A classical invariant is a quantity or property associated with a mathematical object that remains unchanged under a specified group of classical transformations, such as rotations, translations, or linear changes of coordinates.
-
E.
result in equivariant cohomology
A result in equivariant cohomology is a theorem or statement describing how cohomological invariants behave under a group action, typically relating equivariant cohomology groups to ordinary cohomology or geometric data of the action.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:19 a.m.