Triple
T15820470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Data Link Layer |
E383592
|
entity |
| Predicate | OSIModelLayerName |
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: [Data Link Layer, OSIModelLayerName, Layer 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OSIModelLayerName Context triple: [Data Link Layer, OSIModelLayerName, 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.
layerOf
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
D.
networkLevel
Indicates the hierarchical position or tier an entity occupies within a network structure.
-
E.
protocolLayer
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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a7ba4881908a2747bf063d79f1 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.