Triple
T31818852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wien bridge oscillator |
E812208
|
entity |
| Predicate | typicalOutputWaveform |
P39320
|
FINISHED |
| Object | sinusoidal |
—
|
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: sinusoidal | Statement: [Wien bridge oscillator, typicalOutputWaveform, sinusoidal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOutputWaveform Context triple: [Wien bridge oscillator, typicalOutputWaveform, sinusoidal]
-
A.
waveformModel
Indicates that an entity serves as or uses a specific waveform model to represent or generate its signal behavior.
-
B.
hasWaveShape
Indicates that one entity exhibits or possesses a particular wave-like geometric or physical shape in relation to another.
-
C.
waveType
chosen
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
D.
hasTypicalWaves
Indicates that something exhibits the usual or characteristic pattern, form, or behavior of waves associated with it.
-
E.
typicalOutputPowerRange
Indicates the usual range of power output values that an entity typically produces or operates within.
- 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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:45 p.m.