Triple

T1938039
Position Surface form Disambiguated ID Type / Status
Subject DNP3 E41487 entity
Predicate competesWith P1375 FINISHED
Object IEC 60870-5-104 E41486 NE 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: IEC 60870-5-104 | Statement: [DNP3, competesWith, IEC 60870-5-104]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IEC 60870-5-104
Context triple: [DNP3, competesWith, IEC 60870-5-104]
  • A. IEC 60870‑5‑104 chosen
    IEC 60870‑5‑104 is an international standard defining networked telecontrol communication protocols for supervisory control and data acquisition (SCADA) systems over TCP/IP in electrical power systems.
  • B. IEC 60870‑5‑101
    IEC 60870‑5‑101 is an international standard defining basic telecontrol communication protocols for monitoring and controlling electrical power systems over serial links.
  • C. IEC 61850
    IEC 61850 is an international standard that defines communication protocols and data models for automation, protection, and control systems in electrical substations and power utility networks.
  • D. DNP3
    DNP3 (Distributed Network Protocol) is a communication protocol widely used in electric utility and industrial automation systems for reliable, secure, and interoperable data exchange between control equipment and field devices.
  • E. IEEE 1532
    IEEE 1532 is an extension of the JTAG boundary-scan standard that defines in-system programming and configuration procedures for programmable devices such as FPGAs and CPLDs.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a88649b24c819080047f26b6db2ded completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb2c752fc81909baf38ff1cdeb18c completed March 7, 2026, 5:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae1fd173b881909fbd454fc9d7fabb completed March 9, 2026, 1:18 a.m.
Created at: March 4, 2026, 7:36 p.m.