Triple
T11569220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INSAT-2C |
E274339
|
entity |
| Predicate | hasTransponderBand |
P47328
|
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: [INSAT-2C, hasTransponderBand, C-band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransponderBand Context triple: [INSAT-2C, hasTransponderBand, C-band]
-
A.
transponderType
Indicates the specific kind or category of transponder associated with an entity or used in a given context.
-
B.
requiresTransponder
Indicates that one entity must have or use a transponder in order to interact with, access, or be accepted by another entity or system.
-
C.
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.
-
D.
transmissionBand
chosen
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
-
E.
numberOfTransponders
Indicates the quantity of transponders associated with or contained by a given entity.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd543a48190b834abd8e8ae7b65 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.