Triple
T7427867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VTP |
E171413
|
entity |
| Predicate | operatesAtOSIlayer |
P6553
|
FINISHED |
| Object | Layer 2 |
—
|
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: Layer 2 | Statement: [VTP, operatesAtOSIlayer, Layer 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesAtOSIlayer Context triple: [VTP, operatesAtOSIlayer, Layer 2]
-
A.
OSIModelLayer
chosen
Indicates the specific layer within the OSI (Open Systems Interconnection) model at which a networking function, protocol, or interaction operates.
-
B.
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.
-
C.
networkLayerIndependence
Indicates that the relationship or action remains valid and unaffected regardless of the underlying network layer or transport mechanism used.
-
D.
protocolLayer
Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
-
E.
physicalLayer
Indicates a relationship where one entity functions as or pertains to the lowest (physical) layer in a layered system or communication stack, handling the actual transmission of signals or raw data.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f306bfe481909f99f6792de95ffc |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.