Triple
T10991848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwarz lemma |
E259769
|
entity |
| Predicate | coreInequality |
P52976
|
FINISHED |
| Object | |f'(0)| ≤ 1 and |f(z)| ≤ |z| |
—
|
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: |f'(0)| ≤ 1 and |f(z)| ≤ |z| | Statement: [Schwarz lemma, coreInequality, |f'(0)| ≤ 1 and |f(z)| ≤ |z|]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreInequality Context triple: [Schwarz lemma, coreInequality, |f'(0)| ≤ 1 and |f(z)| ≤ |z|]
-
A.
inequality
chosen
Indicates that there is a difference or lack of equality in status, rights, opportunities, or treatment between entities.
-
B.
dataProcessingInequality
Indicates that processing data through a (possibly noisy) transformation cannot increase the information one variable has about another, so the mutual information between them can only stay the same or decrease.
-
C.
coreIdeal
Indicates that something is a fundamental, central principle or value that defines or strongly guides another entity.
-
D.
equalityCondition
Indicates that two values, expressions, or attributes must be exactly the same for the condition to be satisfied.
-
E.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d795d1e918819090c71f5a077fa15a |
completed | April 9, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.