Triple
T29101338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPN2 |
E736645
|
entity |
| Predicate | hasModulationCapability |
P167009
|
FINISHED |
| Object | operator frequency modulation |
—
|
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: operator frequency modulation | Statement: [OPN2, hasModulationCapability, operator frequency modulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModulationCapability Context triple: [OPN2, hasModulationCapability, operator frequency modulation]
-
A.
modulationCapabilities
chosen
Indicates the types or methods of signal modulation that an entity can perform or support.
-
B.
usesModulation
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
C.
definesModulation
Indicates that one entity specifies or determines how another entity is modulated or altered in its behavior, intensity, or effect.
-
D.
isInstrumentCapable
Indicates that an instrument has the capability to perform a specified action or function.
-
E.
hasToneFunction
Indicates that one entity serves a specific tonal or harmonic function in relation to another entity within a musical context.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 28, 2026, 11:12 a.m.