Triple

T8470809
Position Surface form Disambiguated ID Type / Status
Subject Datagram Delivery Protocol E200274 entity
Predicate OSIEquivalent P58587 FINISHED
Object similar to OSI network layer 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: similar to OSI network layer | Statement: [Datagram Delivery Protocol, OSIEquivalent, similar to OSI network layer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: OSIEquivalent
Context triple: [Datagram Delivery Protocol, OSIEquivalent, similar to OSI network layer]
  • A. equivalentTo
    Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
  • B. equivalentIn chosen
    Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
  • C. usesSameSystemAs
    Indicates that two entities operate within or rely on the same underlying system, platform, or infrastructure.
  • D. hasEquivalent
    Indicates that two entities are considered equal in value, meaning, or function within a given context.
  • E. isIsomorphicTo
    Indicates that two structures have a one-to-one, structure-preserving correspondence between their elements, making them equivalent in form even if not identical in content.
  • 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_69ca831a4f348190bfdd09250e86ae35 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe4f234c481909534de6fd702f4cf completed March 31, 2026, 3:14 p.m.
PD Predicate disambiguation batch_69cbd10072cc819084be1ed9ac7ebe9d completed March 31, 2026, 1:49 p.m.
Created at: March 30, 2026, 6:11 p.m.