Triple
T4597228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronecker’s lemma |
E100233
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in real analysis |
C17280
|
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: result in real analysis Context triple: [Kronecker’s lemma, instanceOf, result in real analysis]
-
A.
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.
-
B.
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.
-
C.
result in convex analysis
In convex analysis, a result is a formally stated and proven fact—such as a theorem, lemma, or proposition—that characterizes properties or relationships of convex sets, convex functions, or related optimization structures.
-
D.
result in mathematical physics
A result in mathematical physics is a rigorously proven statement that connects precise mathematical structures with physical theories, often clarifying, justifying, or predicting phenomena within a formal framework.
-
E.
result in probability theory
In probability theory, a result is a formally stated and proven fact—such as a theorem, lemma, or corollary—that describes a property or relationship involving probabilistic concepts like random variables, events, or distributions.
- F. None of above. chosen
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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:11 p.m.