Triple
T322335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 61850 |
E6439
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | IEC 61850‑10 |
E6439
|
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 61850‑10 | Statement: [IEC 61850, hasPart, IEC 61850‑10]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IEC 61850‑10 Context triple: [IEC 61850, hasPart, IEC 61850‑10]
-
A.
IEC 61850
chosen
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.
-
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.
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.
-
D.
IEEE Std 610.12-2010
IEEE Std 610.12-2010 is an updated IEEE standard that provides a formal glossary of terms and definitions used in software engineering.
-
E.
ISO/IEC 23270
ISO/IEC 23270 is the international standard that formally defines the C# programming language specification.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3fe8dde4c8190bd897e5251eb6941 |
completed | March 1, 2026, 8:53 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.