Triple
T73354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.1Q |
E1468
|
entity |
| Predicate | OSIlayer |
P1378
|
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: [IEEE 802.1Q, OSIlayer, Layer 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OSIlayer Context triple: [IEEE 802.1Q, OSIlayer, Layer 2]
-
A.
linkLayer
chosen
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.
-
B.
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.
-
C.
operationalLayer
Indicates that one entity functions as an operational layer or level through which another entity’s activities, processes, or services are executed or managed.
-
D.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
E.
operatesOnLayer
Indicates that an entity performs actions or functions specifically targeting a particular layer within a layered structure or system.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a252201fa481908e30791954119c17 |
completed | Feb. 28, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69a24eacfdc481909e9ff99752fd42bf |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.