Triple
T31041030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 60870‑5‑103 |
E790994
|
entity |
| Predicate | OSIReference |
P43638
|
FINISHED |
| Object | application layer |
—
|
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: application layer | Statement: [IEC 60870‑5‑103, OSIReference, application layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OSIReference Context triple: [IEC 60870‑5‑103, OSIReference, application layer]
-
A.
OSIApproved
Indicates that a software license has been reviewed and approved by the Open Source Initiative (OSI) as complying with its Open Source Definition.
-
B.
isReferenceSystemFor
Indicates that one system serves as the coordinate or measurement framework used to define, locate, or describe positions or values in another system.
-
C.
isImplementationOf
chosen
Indicates that one entity realizes, fulfills, or concretely carries out the specification, interface, or abstract definition provided by another entity.
-
D.
usesReferenceObjects
Indicates that an entity performs an action or makes a determination by relying on one or more other entities as reference points or benchmarks.
-
E.
structureReferences
Indicates that one structure makes reference to, or depends on, another structure.
- 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_69f694f996f081909a1498d6da15358f |
completed | May 3, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.