Triple
T26756939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wigner 3j symbols |
E674699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tensor coupling coefficient |
C10400
|
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: tensor coupling coefficient Context triple: [Wigner 3j symbols, instanceOf, tensor coupling coefficient]
-
A.
model of angular momentum coupling
A model of angular momentum coupling is a conceptual framework that describes how individual angular momenta (such as spin and orbital contributions) combine vectorially to produce total angular momentum and associated quantum states in physical systems.
-
B.
LS coupling
LS coupling is an atomic coupling scheme in which individual electron orbital angular momenta combine to form a total orbital angular momentum L, individual spins combine to form a total spin S, and these then couple to give the total angular momentum J of the atom.
-
C.
tensorial connection coefficient
chosen
A tensorial connection coefficient is a geometric object that encodes how tensor components change under parallel transport or differentiation on a manifold in a way that transforms as a true tensor.
-
D.
coupling constant
A coupling constant is a parameter in a physical theory that quantifies the strength of interaction between fields or particles.
-
E.
Casimir operator
The Casimir operator is a distinguished element of the center of the universal enveloping algebra of a Lie algebra (or Lie group) that commutes with all generators and acts as a scalar on each irreducible representation, thereby classifying those representations.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:56 a.m.