Triple
T849112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starlink user terminal |
E18343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite internet user terminal |
C448
|
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 internet user terminal Context triple: [Starlink user terminal, instanceOf, satellite internet user terminal]
-
A.
telecommunications infrastructure component
A telecommunications infrastructure component is a physical or virtual element—such as cables, antennas, switches, or routers—that enables the transmission, routing, and management of voice, data, and multimedia communications across networks.
-
B.
internet infrastructure component
An internet infrastructure component is a foundational hardware or software element—such as routers, switches, servers, cables, or protocols—that enables the transmission, routing, and reliable delivery of data across interconnected networks.
-
C.
wireless communication device
chosen
A wireless communication device is an electronic apparatus that transmits and receives data over radio or other non-wired signals to enable voice, text, or multimedia communication without physical connections.
-
D.
spacecraft
A spacecraft is a vehicle or device designed to travel beyond Earth's atmosphere for purposes such as exploration, communication, research, or transportation.
-
E.
space communication project
A space communication project is an organized effort to design, develop, and operate systems that enable reliable data and signal exchange between spacecraft, satellites, and ground stations.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.