Triple
T5705483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartan connection |
E125773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | connection in differential geometry |
C3506
|
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: connection in differential geometry Context triple: [Cartan connection, instanceOf, connection in differential geometry]
-
A.
differential geometric object
chosen
A differential geometric object is a mathematical entity, such as a manifold, tensor, or connection, defined on smooth spaces and characterized by properties that are invariant under smooth coordinate transformations.
-
B.
tensorial connection coefficient
A tensorial connection coefficient is a geometric object that encodes how tensor components change under parallel transport or differentiation on a manifold in a way that transforms as a true tensor.
-
C.
branch of differential geometry
A branch of differential geometry is a specialized area of study within differential geometry that focuses on analyzing smooth manifolds and related geometric structures using differential and integral calculus techniques.
-
D.
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.
-
E.
geometric structure
A geometric structure is an abstract mathematical entity defined by sets of points and the relationships between them (such as distances, angles, or incidences) that determine its shape and spatial properties.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:45 p.m.