Triple
T13319824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOSFET |
E317284
|
entity |
| Predicate | controlledByVoltageBetween |
P109504
|
FINISHED |
| Object | gate and source |
—
|
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: gate and source | Statement: [MOSFET, controlledByVoltageBetween, gate and source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByVoltageBetween Context triple: [MOSFET, controlledByVoltageBetween, gate and source]
-
A.
signalVoltage
Indicates the electrical potential level carried by a signal in a circuit or communication channel.
-
B.
typicalSupplyVoltageRange
Indicates the usual minimum-to-maximum voltage range within which a device or component is designed to be normally powered and operate correctly.
-
C.
supplyVoltageRange
Indicates the range of electrical supply voltages within which the entity is designed or allowed to operate.
-
D.
hasExportCableVoltage
Indicates the voltage level at which electrical power is exported through a cable from one system or component to another.
-
E.
hasOpenLoopVoltageGainTypical
Indicates that the relationship specifies the typical value of an entity’s open-loop voltage gain in an electrical or electronic context.
- F. None of above. chosen
Provenance (4 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:29 p.m.