Triple
T9030094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modbus |
E216146
|
entity |
| Predicate | definesOSIModelLayer |
P11823
|
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: [Modbus, definesOSIModelLayer, application layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesOSIModelLayer Context triple: [Modbus, definesOSIModelLayer, application layer]
-
A.
OSIModelLayer
Indicates the specific layer within the OSI (Open Systems Interconnection) model at which a networking function, protocol, or interaction operates.
-
B.
layerOf
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
C.
linkLayer
Indicates a relationship where one entity is connected to another at the data link (Layer 2) level of a network stack, enabling direct frame-level communication between them.
-
D.
layerType
Indicates the specific kind or category of layer that an entity belongs to or is classified as.
-
E.
protocolLayer
chosen
Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9e0aa881908886f453c51ecd0e |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.