Triple
T35529186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Widlar bandgap reference |
E1026751
|
entity |
| Predicate | typicalOutputVoltage |
P120434
|
FINISHED |
| Object | about 1.2 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: about 1.2 V | Statement: [Widlar bandgap reference, typicalOutputVoltage, about 1.2 V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOutputVoltage Context triple: [Widlar bandgap reference, typicalOutputVoltage, about 1.2 V]
-
A.
typicalVoltageRange
Indicates the usual minimum-to-maximum voltage interval within which something is designed or expected to operate.
-
B.
typicalSupplyVoltage
chosen
Indicates the standard or commonly used voltage level at which a device or component is normally supplied or operated.
-
C.
typicalElectricalOutputRange
Indicates the usual range of electrical power or energy output that an entity is expected to produce under normal operating conditions.
-
D.
typicalOutputPowerRange
Indicates the usual range of power output values that an entity typically produces or operates within.
-
E.
voltageInput
Indicates that an entity serves as or provides an electrical voltage supplied to another entity 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_69f76dff7e508190b28ceeee770dce23 |
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:04 p.m.