Triple
T17105217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kramers opacity law |
E415081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astrophysical relation |
C13348
|
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: astrophysical relation Context triple: [Kramers opacity law, instanceOf, astrophysical relation]
-
A.
astrophysical model
An astrophysical model is a theoretical or computational framework that describes and predicts the physical processes, structures, and evolution of astronomical objects and phenomena in the universe.
-
B.
constitutive relation
chosen
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.
astronomical law
An astronomical law is a fundamental principle or rule, derived from observation and theory, that describes consistent patterns and relationships governing celestial bodies and cosmic phenomena.
-
E.
astronomical reference parameter
An astronomical reference parameter is a standardized value or constant used to define, calibrate, or relate measurements in astronomy, such as positions, motions, or physical properties of celestial objects, within a chosen reference frame or system.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.