Triple
T623085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reissner–Nordström metric |
E14555
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | black hole metric |
C326
|
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: black hole metric Context triple: [Reissner–Nordström metric, instanceOf, black hole metric]
-
A.
Eddington–Finkelstein coordinate system
The Eddington–Finkelstein coordinate system is a reformulation of the Schwarzschild spacetime using null (lightlike) coordinates that smoothly extend across the event horizon, eliminating the coordinate singularity present in standard Schwarzschild coordinates.
-
B.
solution in general relativity
chosen
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.
-
C.
Penrose diagram
A Penrose diagram is a spacetime diagram used in general relativity that compactifies infinite regions to finite size, allowing the global causal structure of a spacetime to be visualized.
-
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.
cosmological collapse solution
A cosmological collapse solution is a spacetime model in general relativity or cosmology in which the universe (or a region of it) evolves from expansion or equilibrium into a contracting phase that culminates in a singularity or high-density end state.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.