Triple
T17359557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-band |
E422030
|
entity |
| Predicate | typicalModulation |
P23647
|
FINISHED |
| Object | phase-shift keying |
—
|
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-shift keying | Statement: [X-band, typicalModulation, phase-shift keying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalModulation Context triple: [X-band, typicalModulation, phase-shift keying]
-
A.
definesModulation
Indicates that one entity specifies or determines how another entity is modulated or altered in its behavior, intensity, or effect.
-
B.
usesModulation
chosen
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
C.
demodulatedBy
Indicates that a modulated signal has been processed to extract its original baseband information by a specified demodulation method or device.
-
D.
typicalGainType
Indicates the usual or characteristic type of gain associated with an entity, such as the standard way value or profit is typically obtained.
-
E.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4be7448190988593ee342348c1 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.