Triple
T30040987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NMOS |
E763300
|
entity |
| Predicate | thresholdVoltagePolarity |
P11247
|
FINISHED |
| Object | positive |
—
|
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: positive | Statement: [NMOS, thresholdVoltagePolarity, positive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thresholdVoltagePolarity Context triple: [NMOS, thresholdVoltagePolarity, positive]
-
A.
signalPolarity
chosen
Indicates the directional orientation or sign (positive or negative) of a signal relative to a defined reference.
-
B.
controlledByVoltageBetween
Indicates that the behavior or state of one entity is regulated or determined by the electrical potential difference (voltage) between two other entities.
-
C.
tractionVoltage
Indicates the voltage level supplied to a traction system that powers propulsion or movement.
-
D.
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.
-
E.
electricalPolarity
Indicates that there is a relationship specifying the direction or type of electrical charge or potential difference associated with an entity or connection.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679d8525881909915ac704ab1ac30 |
completed | May 2, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:52 p.m.