Triple
T25920212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauss–Codazzi equations |
E653148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geometric compatibility condition |
C29356
|
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: geometric compatibility condition Context triple: [Gauss–Codazzi equations, instanceOf, geometric compatibility condition]
-
A.
integrability condition
chosen
An integrability condition is a mathematical requirement, often expressed as a compatibility or consistency relation among derivatives, that ensures a given system of equations or differential forms admits a solution or can be derived from a potential function.
-
B.
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.
-
C.
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.
-
D.
geometrical relation
A geometrical relation is an abstract connection or dependency between geometric entities (such as points, lines, and shapes) that specifies how they are positioned, oriented, or measured relative to one another.
-
E.
geodesic structure
A geodesic structure is a framework composed of short, straight elements arranged along geodesic lines on a surface to create a lightweight, stable, and often dome-like form.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:32 a.m.