Triple
T20471079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermite constant |
E502193
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | invariant in the geometry of numbers |
C10588
|
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 in the geometry of numbers Context triple: [Hermite constant, instanceOf, invariant in the geometry of numbers]
-
A.
geometric invariant
chosen
A geometric invariant is a property of a geometric object that remains unchanged under a specified group of transformations, such as rotations, translations, or more general symmetries.
-
B.
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.
-
C.
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.
-
D.
24-dimensional lattice
A 24-dimensional lattice is a discrete, periodic arrangement of points in 24-dimensional Euclidean space generated by integer linear combinations of 24 independent basis vectors.
-
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.
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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:33 a.m.