Triple
T35598720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM10 operational amplifier |
E1028707
|
entity |
| Predicate | minimumOperatingSupplyVoltage |
P131221
|
FINISHED |
| Object | 1.1 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: 1.1 V | Statement: [LM10 operational amplifier, minimumOperatingSupplyVoltage, 1.1 V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumOperatingSupplyVoltage Context triple: [LM10 operational amplifier, minimumOperatingSupplyVoltage, 1.1 V]
-
A.
typicalSupplyVoltage
Indicates the standard or commonly used voltage level at which a device or component is normally supplied or operated.
-
B.
supplyVoltageRange
Indicates the range of electrical supply voltages within which the entity is designed or allowed to operate.
-
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.
minimumVoltageMagnitude
chosen
Indicates the lowest allowable or observed value of an entity’s voltage magnitude within a specified context or range.
-
E.
coreVoltage
Indicates the electrical potential difference supplied to the core component of a device or system.
- 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_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:05 p.m.