Triple
T35281373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub Phatty |
E1018941
|
entity |
| Predicate | hasOscillatorType |
P182279
|
FINISHED |
| Object | voltage-controlled oscillator |
—
|
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: voltage-controlled oscillator | Statement: [Sub Phatty, hasOscillatorType, voltage-controlled oscillator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOscillatorType Context triple: [Sub Phatty, hasOscillatorType, voltage-controlled oscillator]
-
A.
hasOscillationFrequency
Indicates that an entity exhibits oscillatory behavior characterized by a specific frequency value.
-
B.
hasOnChipOscillator
chosen
Indicates that one entity incorporates or is equipped with an oscillator circuit integrated directly on its chip.
-
C.
hasSoundEngineType
Indicates a relationship where an entity is associated with or characterized by a specific type of sound engine.
-
D.
hasAmplifierType
Indicates that an entity is associated with, or characterized by, a specific type or category of amplifier used.
-
E.
oscillatorsPerVoice
Indicates the number of oscillators assigned to or used by each individual voice in a multi-voice (polyphonic) system.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.