Triple
T35662580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM101 operational amplifier |
E1030475
|
entity |
| Predicate | gainBandwidthProduct |
P44395
|
FINISHED |
| Object | on the order of 1 MHz |
—
|
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: on the order of 1 MHz | Statement: [LM101 operational amplifier, gainBandwidthProduct, on the order of 1 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainBandwidthProduct Context triple: [LM101 operational amplifier, gainBandwidthProduct, on the order of 1 MHz]
-
A.
hasGainBandwidthProductTypical
chosen
Indicates that an entity has a specified typical value for its gain–bandwidth product, describing the standard frequency–gain performance characteristic.
-
B.
maxTheoreticalBandwidthPerSlot
Indicates the maximum possible data transfer capacity that can be achieved per individual slot under ideal conditions.
-
C.
hasMaximumBandwidth
Indicates the maximum data transfer capacity that can be allocated, supported, or utilized in a given connection or system.
-
D.
bandwidthEfficiency
Indicates how effectively available bandwidth is utilized to transmit data relative to capacity or resource usage.
-
E.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fa913c48190a609dfd9c184afbc |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.