Triple
T5446345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carathéodory metric |
E122257
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | complex-analytic invariant metric |
C10054
|
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: complex-analytic invariant metric Context triple: [Carathéodory metric, instanceOf, complex-analytic invariant metric]
-
A.
geometric invariant
A geometric invariant is a property of a geometric object that remains unchanged under a specified group of transformations, such as rotations, translations, or more general symmetries.
-
B.
maximal analytic extension
A maximal analytic extension is the largest possible extension of a given spacetime (or manifold with metric) in which the metric and its geodesics can be continued analytically without introducing further removable boundaries or singularities.
-
C.
tool in geometric analysis
chosen
A tool in geometric analysis is a mathematical method, concept, or construction used to study and characterize the geometric and analytic properties of spaces, shapes, and mappings.
-
D.
result in complex analysis
A result in complex analysis is a proven statement or theorem about functions of a complex variable, often revealing deep relationships between analytic, geometric, and topological properties in the complex plane.
-
E.
pseudo-Riemannian manifold
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.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:07 p.m.