Triple
T33157525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSAT-16 |
E848623
|
entity |
| Predicate | extendedCbandTransponders |
P126442
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [GSAT-16, extendedCbandTransponders, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedCbandTransponders Context triple: [GSAT-16, extendedCbandTransponders, 12]
-
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.
satelliteBand
chosen
Indicates that something operates in, uses, or is associated with a specific frequency band within the satellite communication spectrum.
-
D.
numberOfTransponders
Indicates the quantity of transponders associated with or contained by a given entity.
-
E.
transmissionCapacity
Indicates the maximum amount of data or power that can be transmitted through a channel, link, or system over a given period.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:28 a.m.