Triple
T3800206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.5 |
E91668
|
entity |
| Predicate | OSIReferenceModelLayer |
P6553
|
FINISHED |
| Object | Layer 1 |
—
|
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 1 | Statement: [IEEE 802.5, OSIReferenceModelLayer, Layer 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OSIReferenceModelLayer Context triple: [IEEE 802.5, OSIReferenceModelLayer, Layer 1]
-
A.
OSIModelLayer
chosen
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.
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.
layerStructure
Indicates a relationship where one entity is organized in or assigned to a specific layer or hierarchical level within a structured 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.