Triple
T11098920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clebsch–Aronhold invariants |
E262451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | object in invariant theory |
C29200
|
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: object in invariant theory Context triple: [Clebsch–Aronhold invariants, instanceOf, object in invariant theory]
-
A.
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.
-
B.
geometric invariant
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.
-
C.
algebraic variety
An algebraic variety is a geometric object defined as the set of common solutions to a system of polynomial equations over a field, studied up to algebraic and topological properties.
-
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.
work in algebraic geometry
Work in algebraic geometry studies geometric objects defined as solution sets to polynomial equations, using tools from commutative algebra and topology to understand their structure, classification, and morphisms between them.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.