Triple
T28711309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APT |
E729838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite image broadcast format |
C37761
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: satellite image broadcast format Context triple: [APT, instanceOf, satellite image broadcast format]
-
A.
satellite data format
chosen
A satellite data format is a standardized digital structure for encoding, organizing, and storing measurements and imagery collected by satellite sensors to enable consistent processing, analysis, and sharing.
-
B.
broadcast television system
A broadcast television system is an integrated network of equipment, standards, and transmission channels that captures, encodes, and distributes audiovisual content over the air or via cable/satellite to multiple receivers simultaneously.
-
C.
broadcast television standard
A broadcast television standard is a defined set of technical specifications and protocols that govern how video and audio signals are encoded, transmitted, and received for over-the-air television broadcasting.
-
D.
remote sensing satellite
A remote sensing satellite is an orbiting spacecraft equipped with sensors that collect data about the Earth's surface and atmosphere for applications such as mapping, environmental monitoring, and resource management.
-
E.
military satellite
A military satellite is an artificial satellite deployed and operated by armed forces to support defense-related functions such as reconnaissance, communications, navigation, early warning, and targeting.
- F. None of above.
Provenance (1 batch)
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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:48 a.m.