Triple

T4020512
Position Surface form Disambiguated ID Type / Status
Subject IEEE 802.2 E91267 entity
Predicate relationshipToOSI P11823 FINISHED
Object maps OSI network layer services onto IEEE 802 LANs 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: maps OSI network layer services onto IEEE 802 LANs | Statement: [IEEE 802.2, relationshipToOSI, maps OSI network layer services onto IEEE 802 LANs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relationshipToOSI
Context triple: [IEEE 802.2, relationshipToOSI, maps OSI network layer services onto IEEE 802 LANs]
  • A. OSIModelLayer
    Indicates the specific layer within the OSI (Open Systems Interconnection) model at which a networking function, protocol, or interaction operates.
  • B. relationToIETF
    Indicates the nature of an entity’s connection or involvement with the Internet Engineering Task Force (IETF), such as affiliation, participation, or oversight.
  • C. networkLayerIndependence
    Indicates that the relationship or action remains valid and unaffected regardless of the underlying network layer or transport mechanism used.
  • D. usesPhysicalLayerSimilarTo
    Indicates that one entity employs a physical layer that is similar in structure, technology, or operational characteristics to that used by another entity.
  • 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_69aed9618b04819081750d979d2af098 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefaca33e4819091957c7915857a42 completed March 9, 2026, 4:52 p.m.
PD Predicate disambiguation batch_69aef8fc78ec819092d4dab88d85a141 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:35 p.m.