Triple
T29436221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riesz transforms |
E746579
|
entity |
| Predicate | isBoundedOn |
P167173
|
FINISHED |
| Object | L^p(R^n) for 1 < p < ∞ |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: L^p(R^n) for 1 < p < ∞ | Statement: [Riesz transforms, isBoundedOn, L^p(R^n) for 1 < p < ∞]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBoundedOn Context triple: [Riesz transforms, isBoundedOn, L^p(R^n) for 1 < p < ∞]
-
A.
isBounded
Indicates that a quantity, function, or set does not exceed certain fixed limits in magnitude or extent.
-
B.
givesBoundOn
Indicates that one quantity provides an upper or lower limit (a bound) on the value or behavior of another quantity.
-
C.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
D.
isBoundedBelow
Indicates that every value in a set or function is greater than or equal to some fixed lower bound.
-
E.
isUpperBoundFor
Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
- F. None of above. chosen
Provenance (4 batches)
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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66accf77c81908f0f4c1a67e05e47 |
completed | May 2, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 3:16 p.m.