Triple

T30314657
Position Surface form Disambiguated ID Type / Status
Subject Fibre Channel over IP E771027 entity
Predicate encapsulationMedium P33248 FINISHED
Object IP packets 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: IP packets | Statement: [Fibre Channel over IP, encapsulationMedium, IP packets]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: encapsulationMedium
Context triple: [Fibre Channel over IP, encapsulationMedium, IP packets]
  • A. propagationMedium
    Indicates the medium or substance through which something (such as a signal, wave, or influence) is transmitted or propagated.
  • B. encapsulation chosen
    Indicates that one entity encloses, contains, or wraps another entity or set of details within a defined boundary, often hiding internal structure from external access.
  • C. encapsulationDirection
    Indicates the direction in which one entity encloses, contains, or wraps around another within an encapsulation relationship.
  • D. canonicalMedium
    Indicates the primary or standard medium through which something is most authoritatively or typically expressed, distributed, or experienced.
  • E. enclosedInConduits
    Indicates that one entity is physically contained or routed within conduit structures provided by another entity.
  • 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_69f22488f224819081b0f3ec41ab975c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6816f2070819084042f987b1be68f completed May 2, 2026, 10:57 p.m.
PD Predicate disambiguation batch_69f67603526c81908295a1ece8727c66 completed May 2, 2026, 10:09 p.m.
Created at: April 29, 2026, 7:51 p.m.