Triple
T37104521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shapiro delay |
E918804
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | general relativistic effect |
C64379
|
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: general relativistic effect Context triple: [Shapiro delay, instanceOf, general relativistic effect]
-
A.
effect in special relativity
An effect in special relativity is any physical phenomenon—such as time dilation, length contraction, or relativistic mass increase—that arises from the invariance of the speed of light and the relativity of simultaneity between inertial reference frames.
-
B.
frame-dragging effect
The frame-dragging effect is a general relativistic phenomenon in which a rotating massive body twists the surrounding spacetime, causing nearby objects and light paths to be subtly dragged around with its rotation.
-
C.
test of general relativity
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.
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.
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. 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.