Triple

T8602653
Position Surface form Disambiguated ID Type / Status
Subject AppleTalk Session Protocol E203716 entity
Predicate operatesInLayer P6553 FINISHED
Object session 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: session layer | Statement: [AppleTalk Session Protocol, operatesInLayer, session layer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatesInLayer
Context triple: [AppleTalk Session Protocol, operatesInLayer, session layer]
  • A. operatesOnLayer
    Indicates that an entity performs actions or functions specifically targeting a particular layer within a layered structure or system.
  • B. operationalLayer
    Indicates that one entity functions as an operational layer or level through which another entity’s activities, processes, or services are executed or managed.
  • C. layerOf
    Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
  • D. operatesInSegment
    Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
  • E. OSIModelLayer chosen
    Indicates the specific layer within the OSI (Open Systems Interconnection) model at which a networking function, protocol, or interaction operates.
  • 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_69ca832b56948190ba751cec255308f1 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc46da609881909a6d851915e8df14 completed March 31, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69cc454eb2908190acf0e4336bc67e7b completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:24 p.m.