Triple
T13319823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOSFET |
E317284
|
entity |
| Predicate | controlsCurrentBetween |
P77376
|
FINISHED |
| Object | drain 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: drain and source | Statement: [MOSFET, controlsCurrentBetween, drain and source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsCurrentBetween Context triple: [MOSFET, controlsCurrentBetween, drain and source]
-
A.
controlsMovementBetween
Indicates a relationship where one entity regulates, directs, or manages the movement or transfer of another entity between locations or states.
-
B.
controlRange
Indicates the spatial or contextual extent within which an entity can exert control or influence over another entity or process.
-
C.
currentBetween
chosen
Indicates that the current value of a quantity lies within a specified range between two boundary values.
-
D.
controlStatus
Indicates that one entity has a particular level, state, or condition of control over another entity or process.
-
E.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
- 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_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. |
Created at: April 9, 2026, 9:29 p.m.