Triple
T10389283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weil representation |
E244847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | representation of a group |
C27997
|
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: representation of a group Context triple: [Weil representation, instanceOf, representation of a group]
-
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 the Lorentz group
A representation of the Lorentz group is a mathematical structure (typically a vector space with linear operators) on which the Lorentz transformations act in a way that preserves the group operations, allowing physical fields or states to transform consistently under changes of inertial reference frames.
-
C.
two-dimensional representation
A two-dimensional representation is a mapping of abstract elements or data into a flat plane using two axes or coordinates, enabling visualization and analysis of relationships in two spatial dimensions.
-
D.
finite simple group
A finite simple group is a finite group that has no nontrivial normal subgroups, meaning its only normal subgroups are the trivial group and the group itself.
-
E.
finite reflection group
A finite reflection group is a finite group generated by orthogonal reflections of a Euclidean (or more generally, real inner product) space, acting as symmetries that preserve distances and angles.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:05 p.m.