Triple
T29371625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMPS |
E744869
|
entity |
| Predicate | downlinkFrequencyRange |
P1685
|
FINISHED |
| Object | 869–894 MHz |
—
|
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: 869–894 MHz | Statement: [AMPS, downlinkFrequencyRange, 869–894 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: downlinkFrequencyRange Context triple: [AMPS, downlinkFrequencyRange, 869–894 MHz]
-
A.
downlinkMethod
Indicates the method or technology used to transmit data from a remote system (e.g., satellite or spacecraft) down to a receiving station.
-
B.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
C.
multipleAccessSchemeDownlink
Indicates that the downlink transmission uses more than one access scheme simultaneously or in combination.
-
D.
hasCarrierFrequency
Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
-
E.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
- 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_69f669ab36008190bc2e3c5dbdd2050d |
completed | May 2, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:27 p.m.