Triple
T35662582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM101 operational amplifier |
E1030475
|
entity |
| Predicate | inputCommonModeRange |
P182575
|
FINISHED |
| Object | approximately ±12 V at ±15 V supply |
—
|
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: approximately ±12 V at ±15 V supply | Statement: [LM101 operational amplifier, inputCommonModeRange, approximately ±12 V at ±15 V supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputCommonModeRange Context triple: [LM101 operational amplifier, inputCommonModeRange, approximately ±12 V at ±15 V supply]
-
A.
controlRange
Indicates the spatial or contextual extent within which an entity can exert control or influence over another entity or process.
-
B.
configurationRange
chosen
Indicates the span or limits of values or settings that a configuration can take or is defined over.
-
C.
coreRange
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
-
D.
controlCodeRange
Indicates that one entity specifies or constrains the allowable range of control codes applicable to another entity.
-
E.
tuningRange
Indicates the range of values over which something can be tuned or adjusted.
- 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_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.