Triple
T31818845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wien bridge oscillator |
E812208
|
entity |
| Predicate | hasFrequencyFormula |
P81134
|
FINISHED |
| Object | f = 1 / (2πRC) |
—
|
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: f = 1 / (2πRC) | Statement: [Wien bridge oscillator, hasFrequencyFormula, f = 1 / (2πRC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrequencyFormula Context triple: [Wien bridge oscillator, hasFrequencyFormula, f = 1 / (2πRC)]
-
A.
hasGeneralFormula
chosen
Indicates that an entity (such as a class of compounds or expressions) is characterized by a general or canonical formula that represents all its specific instances.
-
B.
hasFrequencyNote
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
-
C.
hasFrequencyCategory
Indicates that something is associated with a particular classification of how often it occurs or is used.
-
D.
hasConnectionFormula
Indicates that there exists a specific formula or expression defining the connection or relationship between the related entities.
-
E.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
- 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_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 30, 2026, 11:45 p.m.