Triple
T35598721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM10 operational amplifier |
E1028707
|
entity |
| Predicate | typicalSupplyCurrent |
P44403
|
FINISHED |
| Object | 270 µA |
—
|
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: 270 µA | Statement: [LM10 operational amplifier, typicalSupplyCurrent, 270 µA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSupplyCurrent Context triple: [LM10 operational amplifier, typicalSupplyCurrent, 270 µA]
-
A.
hasQuiescentSupplyCurrentTypical
chosen
Indicates the typical amount of supply current drawn by a device when it is in a quiescent (idle or no-load) operating state.
-
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.
hasTypicalCurrentRange
Indicates the usual or standard range of electric current values typically associated with or allowed for something.
-
E.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.