Triple
T32023933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pound–Rebka experiment |
E817767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gravitational redshift measurement |
C22448
|
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: gravitational redshift measurement Context triple: [Pound–Rebka experiment, instanceOf, gravitational redshift measurement]
-
A.
radial velocity measurement method
A radial velocity measurement method is a technique used to determine the component of an object's velocity along the line of sight, typically by analyzing Doppler shifts in its spectral lines.
-
B.
cosmological distance duality relation
The cosmological distance duality relation is a fundamental relation in cosmology that links luminosity distance and angular diameter distance through the simple formula \(D_L = (1+z)^2 D_A\), assuming photon number conservation and standard spacetime geometry.
-
C.
test of general relativity
chosen
A test of general relativity is an experimental or observational procedure designed to verify, constrain, or potentially falsify the predictions of Einstein’s theory of gravitation under specific physical conditions.
-
D.
gravitational constant
The gravitational constant is a fundamental physical constant that quantifies the strength of the gravitational force between two masses in Newton's law of universal gravitation.
-
E.
tool in general relativity
A tool in general relativity is any mathematical, conceptual, or computational method used to formulate, analyze, or solve problems involving the curvature of spacetime and its interaction with matter and energy.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:17 a.m.