Triple
T28533542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Positioning System satellites |
E722101
|
entity |
| Predicate | signalModulation |
P94939
|
FINISHED |
| Object | CDMA |
—
|
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: CDMA | Statement: [Global Positioning System satellites, signalModulation, CDMA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalModulation Context triple: [Global Positioning System satellites, signalModulation, CDMA]
-
A.
definesModulation
Indicates that one entity specifies or determines how another entity is modulated or altered in its behavior, intensity, or effect.
-
B.
signalingMode
chosen
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
-
C.
demodulatedBy
Indicates that a modulated signal has been processed to extract its original baseband information by a specified demodulation method or device.
-
D.
digitalSignal
Indicates that the relationship or action involves representing, transmitting, or processing information as a discrete-time, discrete-value (digital) signal between entities.
-
E.
signalGenerationMethod
Indicates the method or technique used to produce or generate a signal in a given 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 3:30 a.m.