Triple
T1986294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerr–Newman black hole |
E43148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | type D Petrov spacetime |
C3971
|
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: type D Petrov spacetime Context triple: [Kerr–Newman black hole, instanceOf, type D Petrov spacetime]
-
A.
Lorentzian manifold
A Lorentzian manifold is a smooth manifold equipped with a metric tensor of signature \((-+\cdots+)\) (or its variants) that models spacetime in general relativity by distinguishing timelike, spacelike, and null directions.
-
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.
pseudo-Riemannian manifold
chosen
A pseudo-Riemannian manifold is a smooth manifold equipped with a nondegenerate, symmetric metric tensor of arbitrary signature that allows measurement of lengths and angles, including those with indefinite sign as in spacetime geometry.
-
D.
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.
-
E.
spacetime coordinate chart
A spacetime coordinate chart is a mapping that assigns a unique set of numerical coordinates to each event in a region of spacetime, providing a local reference frame for describing physical phenomena.
- 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.