Triple
T10389284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weil representation |
E244847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | object in representation theory |
C3507
|
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 representation theory Context triple: [Weil representation, instanceOf, object in representation 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.
mathematical object
chosen
A mathematical object is an abstract entity, such as a number, function, set, or space, defined by precise properties and relations within a formal mathematical system.
-
C.
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.
-
D.
object in general relativity
An object in general relativity is any localized concentration of energy–momentum whose presence curves spacetime and thereby influences the motion of matter and light.
-
E.
concept in Lie theory
A concept in Lie theory is an abstract mathematical construct—such as a Lie group, Lie algebra, or representation—that captures continuous symmetries and their algebraic and geometric properties.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:05 p.m.