Triple
T4384228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemaître–Hubble law |
E99201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | empirical relation |
C10297
|
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: empirical relation Context triple: [Lemaître–Hubble law, instanceOf, empirical relation]
-
A.
empirical observation
Empirical observation is the process of gathering information about phenomena through direct sensory experience or measurement, forming the basis for evidence-based conclusions.
-
B.
constitutive relation
A constitutive relation is a mathematical or physical law that links field variables (such as stress and strain or electric field and polarization) to characterize how a specific material or medium responds to external influences.
-
C.
relation in particle physics
A relation in particle physics is a mathematical or conceptual connection—often expressed as an equation or symmetry—linking physical quantities, particles, or interactions in a way that constrains or predicts their behavior.
-
D.
experimental formula
chosen
An experimental formula is a provisional mathematical or symbolic expression derived from empirical observations or trials, used to predict or describe behavior under specific experimental conditions and subject to refinement or validation.
-
E.
Euclidean correlation function
A Euclidean correlation function is a Green’s function defined in Euclidean (imaginary-time) spacetime that encodes the correlations between field operators at different points and is related to physical, real-time correlation functions by analytic continuation.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:19 p.m.