Triple
T18495128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardy space |
E451925
|
entity |
| Predicate | domainOfParameter |
P79472
|
FINISHED |
| Object | 0 < 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: 0 < p ≤ ∞ | Statement: [Hardy space, domainOfParameter, 0 < p ≤ ∞]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainOfParameter Context triple: [Hardy space, domainOfParameter, 0 < p ≤ ∞]
-
A.
domainOfq
chosen
Indicates that a given entity serves as the domain (set of permissible inputs or arguments) for the quantity or relation denoted by q.
-
B.
domainOfVariables
Indicates that the predicate specifies the set or type of values that the variables involved in an expression or formula are allowed to take.
-
C.
domainOfInterpretation
Indicates that the specified set constitutes the universe of discourse over which all variables and quantifiers in a logical system are interpreted.
-
D.
partOfDomain
Indicates that one entity belongs to, is included within, or is a constituent part of the scope or domain defined by another entity.
-
E.
domainOfPosition
Indicates that something specifies or defines the domain (scope, area, or field) within which a particular position or role is applicable.
- F. None of above.
Provenance (3 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532bfeef4819096b2fa28abb662b9 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.