Triple
T11918980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitting lemma |
E283604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in group theory |
C30620
|
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: result in group theory Context triple: [Fitting lemma, instanceOf, result in group theory]
-
A.
result in representation theory
A result in representation theory is a proven statement describing how algebraic structures, such as groups or algebras, can be represented by linear transformations on vector spaces and how these representations behave or decompose.
-
B.
representation of a group
A representation of a group is a homomorphism from that group into the group of linear transformations of a vector space, allowing the group’s abstract elements to be studied via concrete matrices or operators.
-
C.
collection of decision problems in group theory
A collection of decision problems in group theory is a conceptual class comprising questions that ask, for various groups and inputs, whether certain algebraic properties or relations hold, such as the word, conjugacy, or isomorphism problems.
-
D.
abelian group
An abelian group is a set equipped with an associative binary operation that has an identity element and inverses for every element, and for which the operation is commutative.
-
E.
result in probability theory
In probability theory, a result is a formally stated and proven fact—such as a theorem, lemma, or corollary—that describes a property or relationship involving probabilistic concepts like random variables, events, or distributions.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.