Triple
T11918932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitting subgroup |
E283603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgroup invariant |
C17168
|
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: subgroup invariant Context triple: [Fitting subgroup, instanceOf, subgroup invariant]
-
A.
subgroup
chosen
A subgroup is a subset of a group that is itself a group under the same binary operation, containing the identity, inverses, and being closed under the operation.
-
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.
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.
-
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.
pseudogroup
A pseudogroup is a collection of local homeomorphisms (or diffeomorphisms) on a topological space that is closed under composition, inversion, restriction to open subsets, and gluing of compatible local maps, generalizing the notion of a group action to local symmetries.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.