Triple

T54000
Position Surface form Disambiguated ID Type / Status
Subject HTTP E1064 entity
Predicate layerInOSIModel P2393 FINISHED
Object application 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: application layer | Statement: [HTTP, layerInOSIModel, application layer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: layerInOSIModel
Context triple: [HTTP, layerInOSIModel, application layer]
  • A. 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.
  • 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. meetsAtLevel
    Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
  • D. operatesInSegment
    Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
  • E. hasLevel chosen
    Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
  • 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_69a248adc5b48190aa8db9fb092fb28a completed Feb. 28, 2026, 1:45 a.m.
NER Named-entity recognition batch_69a24b3a9e848190b80de3c858678b3a completed Feb. 28, 2026, 1:56 a.m.
PD Predicate disambiguation batch_69a24ac52fb08190aa7c38f83434f795 completed Feb. 28, 2026, 1:54 a.m.
Created at: Feb. 28, 2026, 1:50 a.m.