Triple
T27567620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oseledec splitting |
E695945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | invariant splitting |
C52931
|
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: invariant splitting Context triple: [Oseledec splitting, instanceOf, invariant splitting]
-
A.
integer-valued invariant
An integer-valued invariant is a property of a mathematical object that assigns an integer in a way that remains unchanged under a specified class of transformations or equivalences.
-
B.
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.
-
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.
decomposition theorem
The decomposition theorem is a fundamental result in algebraic geometry and topology stating that, under suitable conditions, the direct image of an intersection complex under a proper map splits as a direct sum of shifted semisimple perverse sheaves.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:42 p.m.