Triple
T31733281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMOS technology |
E809918
|
entity |
| Predicate | usesTransistorPolarity |
P182422
|
FINISHED |
| Object | nMOS |
—
|
NE NERFINISHED |
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: nMOS | Statement: [CMOS technology, usesTransistorPolarity, nMOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTransistorPolarity Context triple: [CMOS technology, usesTransistorPolarity, nMOS]
-
A.
transistorType
Indicates the specific kind or category of transistor associated with an entity (e.g., BJT, MOSFET, JFET).
-
B.
electricalPolarity
Indicates that there is a relationship specifying the direction or type of electrical charge or potential difference associated with an entity or connection.
-
C.
signalPolarityConvention
Indicates the convention used to define which signal polarity (e.g., positive vs. negative or active-high vs. active-low) corresponds to a given logical or functional state in a system.
-
D.
transistorCount
Indicates the number of transistors contained within an electronic component or device.
-
E.
signalPolarity
Indicates the directional orientation or sign (positive or negative) of a signal relative to a defined reference.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: April 30, 2026, 11:22 p.m.