Triple
T7490025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hafele–Keating experiment |
E176981
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | test of general relativity |
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: test of general relativity Context triple: [Hafele–Keating experiment, instanceOf, test of general relativity]
-
A.
equivalence principle test
An equivalence principle test is an experimental investigation designed to determine whether all forms of matter and energy experience the same acceleration in a gravitational field, thereby probing the foundation of general relativity.
-
B.
test of special relativity
A test of special relativity is an experimental or observational procedure designed to verify or constrain the predictions of Einstein’s theory regarding the constancy of the speed of light and the relativity of space and time between inertial frames.
-
C.
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.
-
D.
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.
-
E.
solution in general relativity
A solution in general relativity is a specific spacetime metric (and accompanying matter fields, if any) that satisfies Einstein’s field equations for a given physical configuration or set of conditions.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:43 p.m.