Triple
T1986291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerr–Newman black hole |
E43148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rotating charged black hole |
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: rotating charged black hole Context triple: [Kerr–Newman black hole, instanceOf, rotating charged black hole]
-
A.
non-singular black hole model
A non-singular black hole model is a theoretical description of a black hole whose core avoids the classical spacetime singularity, typically by invoking modified gravity or quantum effects that yield a finite, regular interior geometry.
-
B.
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.
-
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.
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.
-
E.
quantum effect near event horizon
A quantum effect near an event horizon is a phenomenon arising from quantum field fluctuations in the intense gravitational boundary of a black hole, leading to processes such as particle creation and Hawking radiation.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.