Triple
T31041026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 60870‑5‑103 |
E790994
|
entity |
| Predicate | typicalSlaveDevice |
P99560
|
FINISHED |
| Object | protection relay |
—
|
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: protection relay | Statement: [IEC 60870‑5‑103, typicalSlaveDevice, protection relay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSlaveDevice Context triple: [IEC 60870‑5‑103, typicalSlaveDevice, protection relay]
-
A.
typicalServerDevice
Indicates that the subject is a device that is commonly or characteristically used as a server in typical scenarios.
-
B.
controlDeviceTypical
Indicates that an entity typically operates or manages the functioning of a device.
-
C.
characteristicDevice
chosen
Indicates that a device is a defining or typical instrument, tool, or equipment associated with a particular entity, context, or activity.
-
D.
roleOfDevice
Indicates that a device participates in a situation or system with a specified functional role or purpose.
-
E.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted with.
- 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.