Triple

T15838243
Position Surface form Disambiguated ID Type / Status
Subject ETSI EN 302 307 E384036 entity
Predicate definesModulation P119850 FINISHED
Object QPSK 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: QPSK | Statement: [ETSI EN 302 307, definesModulation, QPSK]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definesModulation
Context triple: [ETSI EN 302 307, definesModulation, QPSK]
  • A. usesModulation
    Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
  • B. modulates
    Indicates that one entity adjusts, regulates, or alters the intensity, frequency, or effect of another entity or process.
  • C. 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.
  • D. videoModulation
    Indicates a relationship where one entity alters or controls the characteristics of a video signal or stream, such as its amplitude, frequency, or encoding parameters.
  • E. modalityOf
    Indicates that one element specifies the manner, mood, or mode in which the action, event, or state expressed by another element is realized or presented.
  • F. None of above. chosen

Provenance (4 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e142e3d48c8190ad0d0af89d062101 completed April 16, 2026, 8:13 p.m.
PD Predicate disambiguation batch_69e005418f588190824d91ff7974dada completed April 15, 2026, 9:38 p.m.
PDg Predicate description generation batch_69e007647f908190adb178c68c7bb7cf completed April 15, 2026, 9:47 p.m.
Created at: April 10, 2026, 4:49 a.m.