Triple
T23210978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zames–Falb multipliers |
E580592
|
entity |
| Predicate | typicalProperty |
P151371
|
FINISHED |
| Object | nonnegative real part over frequency range |
—
|
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: nonnegative real part over frequency range | Statement: [Zames–Falb multipliers, typicalProperty, nonnegative real part over frequency range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProperty Context triple: [Zames–Falb multipliers, typicalProperty, nonnegative real part over frequency range]
-
A.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
B.
typicalItem
Indicates that an item is a representative or characteristic example of a broader category, class, or set.
-
C.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
D.
basisProperty
Indicates that one property serves as the foundational or defining basis for another property or characteristic.
-
E.
propertiesType
Indicates that one entity is classified as a specific type or category of properties associated with another entity.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f191614bc4819080938752d843dcc6 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:07 p.m.