Triple
T31041025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 60870‑5‑103 |
E790994
|
entity |
| Predicate | typicalMasterDevice |
P99560
|
FINISHED |
| Object | substation control system |
—
|
LITERAL 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: substation control system | Statement: [IEC 60870‑5‑103, typicalMasterDevice, substation control system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMasterDevice Context triple: [IEC 60870‑5‑103, typicalMasterDevice, substation control system]
-
A.
roleOfDevice
Indicates that a device participates in a situation or system with a specified functional role or purpose.
-
B.
characteristicDevice
chosen
Indicates that a device is a defining or typical instrument, tool, or equipment associated with a particular entity, context, or activity.
-
C.
wearerDevice
Indicates that a device is worn or carried by a particular entity (the wearer).
-
D.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
E.
targetedDeviceType
Indicates the specific type or category of device that is the intended target of an action, configuration, or content.
- F. None of above.
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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:59 p.m.