Triple
T21145393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lempert function on convex domains |
E521040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | holomorphic invariant |
C10588
|
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: holomorphic invariant Context triple: [Lempert function on convex domains, instanceOf, holomorphic invariant]
-
A.
analytic function
An analytic function is a complex-valued function that is locally given by a convergent power series, meaning it is differentiable at every point in its domain and in a neighborhood around each point.
-
B.
geometric invariant
chosen
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.
-
C.
homological invariant
A homological invariant is a quantity or structure derived from homology theory that remains unchanged under specified transformations, used to distinguish and classify mathematical objects up to an appropriate notion of equivalence.
-
D.
classical invariant
A classical invariant is a quantity or property associated with a mathematical object that remains unchanged under a specified group of classical transformations, such as rotations, translations, or linear changes of coordinates.
-
E.
operation on analytic functions
An operation on analytic functions is a rule or transformation that takes one or more analytic (holomorphic) functions as input and produces another function, typically preserving analyticity within a given domain.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:58 p.m.