Triple
T33697506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iridium OpenPort |
E863355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime broadband service |
C7194
|
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: maritime broadband service Context triple: [Iridium OpenPort, instanceOf, maritime broadband service]
-
A.
mobile satellite service system
A mobile satellite service system is a communication network that uses satellites to provide voice, data, and messaging connectivity to mobile users over wide geographic areas, including remote and underserved regions.
-
B.
Internet service
chosen
An Internet service is a digital offering that provides users with specific online functionality or resources over a network, such as communication, data storage, or content access.
-
C.
maritime mobile service identity
A maritime mobile service identity (MMSI) is a unique nine-digit number assigned to a ship, coast station, or other maritime radio station to identify it in digital communications and safety systems.
-
D.
wireless backhaul solution
A wireless backhaul solution is a high-capacity wireless communication system that connects distributed network access points (such as cell sites or Wi‑Fi hotspots) to the core network, enabling data transport without relying on wired infrastructure.
-
E.
public service broadcasting
Public service broadcasting is a media system, typically funded by the public or through license fees, that provides impartial, high-quality content designed to inform, educate, and entertain while serving the democratic, cultural, and social needs of society rather than commercial interests.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.