Triple
T31818846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wien bridge oscillator |
E812208
|
entity |
| Predicate | frequencyControlledBy |
P13344
|
FINISHED |
| Object | resistor values |
—
|
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: resistor values | Statement: [Wien bridge oscillator, frequencyControlledBy, resistor values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyControlledBy Context triple: [Wien bridge oscillator, frequencyControlledBy, resistor values]
-
A.
frequencyDependsOn
chosen
Indicates that the frequency of one event, action, or state is determined or influenced by another factor or condition.
-
B.
frequencyGivenBy
Indicates that the frequency of something is specified, determined, or provided by a particular source or entity.
-
C.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
D.
frequencyChange
Indicates a change in how often an event, action, or state occurs over time.
-
E.
frequencyCategory
Indicates how often an action, event, or relationship occurs, typically by assigning it to a qualitative frequency level (e.g., rare, occasional, frequent).
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 30, 2026, 11:45 p.m.