Triple
T9029991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harris Controls Division |
E216143
|
entity |
| Predicate | developed |
P73
|
FINISHED |
| Object | DNP3 |
E41487
|
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: DNP3 | Statement: [Harris Controls Division, developed, DNP3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DNP3 Context triple: [Harris Controls Division, developed, DNP3]
-
A.
DNP3
chosen
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.
-
B.
IEC 60870‑5‑104
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.
-
C.
Sercos III
Sercos III is a real-time industrial Ethernet communication standard widely used for high-performance motion control and automation systems.
-
D.
DNP
DNP is the commonly used abbreviation for the Division of Nuclear Physics, a professional organization focused on research and advancement in nuclear physics.
-
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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9e0aa881908886f453c51ecd0e |
completed | April 1, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d01773694c8190830f9294c3ec4f54 |
completed | April 3, 2026, 7:39 p.m. |
Created at: March 30, 2026, 7:08 p.m.