Triple
T25319625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dedekind number |
E634841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combinatorial invariant |
C44533
|
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: combinatorial invariant Context triple: [Dedekind number, instanceOf, combinatorial invariant]
-
A.
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.
-
B.
combinatorial concept
chosen
A combinatorial concept is an abstract idea or principle involving the arrangement, selection, or counting of discrete objects according to specified rules or patterns.
-
C.
combinatorial basis
A combinatorial basis is a minimal set of combinatorial objects or elements from which all structures in a given class can be uniquely generated or represented, typically without redundancy.
-
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.
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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:28 p.m.