Triple
T33183314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSAT-18 |
E849393
|
entity |
| Predicate | usesFrequencyBandForTelecom |
P171922
|
FINISHED |
| Object | C-band |
—
|
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: C-band | Statement: [GSAT-18, usesFrequencyBandForTelecom, C-band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFrequencyBandForTelecom Context triple: [GSAT-18, usesFrequencyBandForTelecom, C-band]
-
A.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
B.
spectralBandUse
Indicates how specific spectral bands are utilized or applied within a given context or process.
-
C.
telecommunicationsBand
chosen
Indicates a relationship where a specific telecommunications frequency band is used, allocated, or associated with a communication system, service, or technology.
-
D.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
E.
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.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:29 a.m.