Triple
T6938833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rydberg constant |
E160621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spectroscopic constant |
C6924
|
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: spectroscopic constant Context triple: [Rydberg constant, instanceOf, spectroscopic constant]
-
A.
spectroscopic parameter
chosen
A spectroscopic parameter is a quantitative value that characterizes how a system interacts with electromagnetic radiation, such as frequencies, intensities, or line shapes observed in a spectrum.
-
B.
spectroscopic approximation
A spectroscopic approximation is a simplified theoretical or computational model used to estimate spectroscopic properties (such as energy levels, transition frequencies, or intensities) by neglecting or approximating certain physical effects to make calculations tractable.
-
C.
spectroscopic effect
A spectroscopic effect is any observable change or feature in a spectrum—such as shifts, splittings, intensity variations, or line broadenings—that arises from the interaction of electromagnetic radiation with matter and reveals information about a system’s structure, dynamics, or environment.
-
D.
Einstein coefficient
The Einstein coefficient is a parameter in quantum theory that quantifies the probability per unit time of spontaneous or stimulated emission or absorption of radiation by an atom or molecule transitioning between energy levels.
-
E.
physical constant
A physical constant is a fundamental, invariant quantity in nature that has a fixed numerical value and characterizes the behavior of physical laws.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:28 p.m.