Triple
T35662579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM101 operational amplifier |
E1030475
|
entity |
| Predicate | slewRate |
P44396
|
FINISHED |
| Object | on the order of 0.5 V/µs to 1 V/µs |
—
|
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: on the order of 0.5 V/µs to 1 V/µs | Statement: [LM101 operational amplifier, slewRate, on the order of 0.5 V/µs to 1 V/µs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slewRate Context triple: [LM101 operational amplifier, slewRate, on the order of 0.5 V/µs to 1 V/µs]
-
A.
hasSlewRateTypical
chosen
Indicates that an entity is characterized by a specified typical (nominal) slew rate value.
-
B.
referenceRate
Indicates that one entity serves as the benchmark or base rate used to determine or adjust the rate applied to another entity or transaction.
-
C.
canSlew
Indicates that an entity has the capability to rotate or reorient another entity (or itself) in angle or direction.
-
D.
ramSpeed
Indicates the rate or velocity at which one entity forcefully collides with or rams into another.
-
E.
hasSlowMovement
Indicates that an entity exhibits movement that is slower than a normal or expected speed.
- 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_69f79fa913c48190a609dfd9c184afbc |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.