Triple
T35662559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM101 operational amplifier |
E1030475
|
entity |
| Predicate | maximumSupplyVoltage |
P10795
|
FINISHED |
| Object | ±22 V |
—
|
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: ±22 V | Statement: [LM101 operational amplifier, maximumSupplyVoltage, ±22 V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSupplyVoltage Context triple: [LM101 operational amplifier, maximumSupplyVoltage, ±22 V]
-
A.
maxVoltage
chosen
Indicates the maximum electrical potential (voltage) that an entity can safely or normally handle, provide, or operate at.
-
B.
typicalSupplyVoltage
Indicates the standard or commonly used voltage level at which a device or component is normally supplied or operated.
-
C.
typicalSupplyVoltageRange
Indicates the usual minimum-to-maximum voltage range within which a device or component is designed to be normally powered and operate correctly.
-
D.
supportsMaximumVoltage
Indicates that an entity is capable of safely operating at or up to a specified maximum voltage level.
-
E.
supplyVoltageRange
Indicates the range of electrical supply voltages within which the entity is designed or allowed to operate.
- 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_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:05 p.m.