Triple
T25956674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SATCOM Ku-1 |
E645421
|
entity |
| Predicate | hasTranspondersInBand |
P126442
|
FINISHED |
| Object | Ku 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: Ku band | Statement: [SATCOM Ku-1, hasTranspondersInBand, Ku band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTranspondersInBand Context triple: [SATCOM Ku-1, hasTranspondersInBand, Ku band]
-
A.
hasTransponders
Indicates that one entity possesses, is equipped with, or includes one or more transponders in relation to another entity or context.
-
B.
transmissionBand
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
-
C.
numberOfTransponders
Indicates the quantity of transponders associated with or contained by a given entity.
-
D.
satelliteBand
chosen
Indicates that something operates in, uses, or is associated with a specific frequency band within the satellite communication spectrum.
-
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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 22, 2026, 8:46 a.m.