Triple
T22695591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Si(Li) detector |
E561163
|
entity |
| Predicate | requiresBiasVoltage |
P149342
|
FINISHED |
| Object | reverse bias |
—
|
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: reverse bias | Statement: [Si(Li) detector, requiresBiasVoltage, reverse bias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresBiasVoltage Context triple: [Si(Li) detector, requiresBiasVoltage, reverse bias]
-
A.
hasInputOffsetVoltageTypical
Indicates the typical (average or nominal) value of the input offset voltage associated with a device or component in this relationship.
-
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.
hasInputOffsetVoltageMax
Indicates the maximum allowable input offset voltage present between the inputs of a device under specified conditions.
-
D.
hasInputBiasCurrentTypical
Indicates that an entity (such as a device or component) has a specified typical value for its input bias current.
-
E.
signalVoltage
Indicates the electrical potential level carried by a signal in a circuit or communication channel.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789e05d88190b9d51bb3f8e3e9d4 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:14 p.m.