Triple
T19258812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 60870 |
E481591
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SCADA communication standard |
C2790
|
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: SCADA communication standard Context triple: [IEC 60870, instanceOf, SCADA communication standard]
-
A.
substation automation standard
chosen
A substation automation standard defines the protocols, architectures, and requirements that enable interoperable, secure, and automated monitoring, control, and protection of electrical substations.
-
B.
fieldbus system
A fieldbus system is an industrial network architecture that connects and coordinates field devices such as sensors and actuators with controllers for real-time data exchange and process automation.
-
C.
EIA standard
An EIA standard is a set of technical guidelines and specifications developed by the Electronic Industries Alliance to ensure compatibility, safety, and interoperability of electronic components and systems.
-
D.
EV charging communication standard
A standardized set of protocols and message formats that enable interoperable, secure communication between electric vehicles, charging stations, and backend systems for managing charging sessions and related services.
-
E.
IEC system
An IEC system is an Interactive Evolutionary Computation framework in which human users iteratively evaluate and select candidate solutions so that an evolutionary algorithm can optimize designs, media, or parameters based on subjective preferences.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:28 p.m.