Triple
T29372184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YM-2151 |
E744882
|
entity |
| Predicate | hasModulationType |
P167009
|
FINISHED |
| Object | phase 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: phase modulation | Statement: [YM-2151, hasModulationType, phase modulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModulationType Context triple: [YM-2151, hasModulationType, phase modulation]
-
A.
usesModulation
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
B.
definesModulation
Indicates that one entity specifies or determines how another entity is modulated or altered in its behavior, intensity, or effect.
-
C.
modulationCapabilities
chosen
Indicates the types or methods of signal modulation that an entity can perform or support.
-
D.
hasAmplifierType
Indicates that an entity is associated with, or characterized by, a specific type or category of amplifier used.
-
E.
audioModulation
Indicates a relationship where one audio signal or parameter is used to vary or control another audio signal’s characteristics (such as amplitude, frequency, or timbre) 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 2:28 p.m.