Triple
T35662581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM101 operational amplifier |
E1030475
|
entity |
| Predicate | openLoopGain |
P44394
|
FINISHED |
| Object | on the order of 100 dB |
—
|
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 100 dB | Statement: [LM101 operational amplifier, openLoopGain, on the order of 100 dB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openLoopGain Context triple: [LM101 operational amplifier, openLoopGain, on the order of 100 dB]
-
A.
hasOpenLoopVoltageGainTypical
chosen
Indicates that the relationship specifies the typical value of an entity’s open-loop voltage gain in an electrical or electronic context.
-
B.
isLoopOf
Indicates that one entity represents a loop or cyclic structure corresponding to, derived from, or associated with another entity.
-
C.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
D.
controlSystems
Indicates that one entity directs, regulates, or manages the behavior or operation of another system or process.
-
E.
hasInclinedLoop
Indicates that one entity features or contains a loop that is positioned at an angle rather than being level or vertical.
- 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.