Triple
T20627435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevanlinna–Pick interpolation |
E506854
|
entity |
| Predicate | typeOfConstraint |
P35662
|
FINISHED |
| Object | interpolation with norm bound |
—
|
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: interpolation with norm bound | Statement: [Nevanlinna–Pick interpolation, typeOfConstraint, interpolation with norm bound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfConstraint Context triple: [Nevanlinna–Pick interpolation, typeOfConstraint, interpolation with norm bound]
-
A.
elementTypeConstraint
Indicates that there is a restriction or rule specifying which types of elements are allowed or required in a given context.
-
B.
typeOfCondition
chosen
Indicates that one condition is a specific kind, category, or subtype of another condition.
-
C.
typeOfRule
Indicates that one rule is classified as a specific kind or category of another, more general rule.
-
D.
hasTypeOfRestriction
Indicates that an entity is subject to a specific kind or category of restriction that limits its use, access, or behavior.
-
E.
constrainedBy
Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe645888190b639ebedc5b3041a |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:42 a.m.