Triple
T849139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starlink user terminal |
E18343
|
entity |
| Predicate | communicatesVia |
P2798
|
FINISHED |
| Object | radio frequency links |
—
|
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: radio frequency links | Statement: [Starlink user terminal, communicatesVia, radio frequency links]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicatesVia Context triple: [Starlink user terminal, communicatesVia, radio frequency links]
-
A.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
B.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
-
C.
isTransmittedBy
Indicates that something (such as information, a signal, or a disease) is passed or conveyed from one entity to another through a specified agent or medium.
-
D.
communicationModelRole
Indicates the role an entity plays within a communication model, specifying its function or position in the communication process.
-
E.
negotiatedVia
Indicates that an agreement, deal, or arrangement was reached through the use of a specific intermediary, channel, or method of negotiation.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac1fac3481909cba7070ce31a9b3 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa807adc8190ad808a573cf8e923 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.