Triple
T4552399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardy–Littlewood maximal function |
E120395
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | object in real analysis |
C3507
|
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: object in real analysis Context triple: [Hardy–Littlewood maximal function, instanceOf, object in real analysis]
-
A.
mathematical object
chosen
A mathematical object is an abstract entity, such as a number, function, set, or space, defined by precise properties and relations within a formal mathematical system.
-
B.
object in general relativity
An object in general relativity is any localized concentration of energy–momentum whose presence curves spacetime and thereby influences the motion of matter and light.
-
C.
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.
-
D.
geometric object
A geometric object is an abstract entity defined by points, lines, surfaces, or volumes in space, characterized by properties such as shape, size, position, and orientation.
-
E.
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.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
Created at: March 20, 2026, 1:09 p.m.