Triple
T31041005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 60870‑5‑103 |
E790994
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | telecontrol protocol |
C993
|
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: telecontrol protocol Context triple: [IEC 60870‑5‑103, instanceOf, telecontrol protocol]
-
A.
communications controller
A communications controller is a hardware or software component that manages, coordinates, and regulates data exchange between devices or networks, ensuring reliable and efficient communication.
-
B.
communication protocol
chosen
A communication protocol is a defined set of rules and formats that enable reliable, structured exchange of data between two or more communicating entities in a networked system.
-
C.
remote control
A remote control is a handheld device that wirelessly sends commands to operate electronic equipment from a distance.
-
D.
Ethernet control protocol
Ethernet control protocol is a conceptual class that manages the configuration, coordination, and regulation of data transmission over Ethernet networks, including flow control, error handling, and link management.
-
E.
communication protocol suite
A communication protocol suite is a coordinated set of network protocols that work together across different layers to enable reliable data exchange between devices in a communication system.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.