Triple
T34689247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton’s Harnack inequalities for Ricci flow |
E890839
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geometric analysis result |
C10469
|
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 analysis result Context triple: [Hamilton’s Harnack inequalities for Ricci flow, instanceOf, geometric analysis result]
-
A.
tool in geometric analysis
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.
-
B.
functional analysis result
A functional analysis result is a formal conclusion or theorem that characterizes the behavior, structure, or properties of functions and operators on infinite-dimensional spaces, typically within the framework of normed, Banach, or Hilbert spaces.
-
C.
result in complex differential geometry
A result in complex differential geometry is a proven theorem or proposition that describes how geometric structures on complex manifolds behave under conditions involving both complex-analytic and differential properties.
-
D.
result in geometry
chosen
A result in geometry is a proven statement or theorem that describes a specific property, relationship, or behavior of geometric figures and spaces.
-
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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.