Triple

T27755043
Position Surface form Disambiguated ID Type / Status
Subject Ultrix E701313 entity
Predicate networkStackOrigin P166194 FINISHED
Object BSD networking code 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: BSD networking code | Statement: [Ultrix, networkStackOrigin, BSD networking code]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: networkStackOrigin
Context triple: [Ultrix, networkStackOrigin, BSD networking code]
  • A. networkStack
    Indicates a relationship where one component or layer is part of, or operates within, a structured hierarchy of networking layers (a network stack) to enable communication.
  • B. networkIntended
    Indicates that one entity is designed or purposed to be used within, connected to, or operate over a particular network or networking context.
  • C. networkService
    Indicates that one entity provides or participates in a network-based service or functionality for another entity or system.
  • D. networkHost
    Indicates that one entity serves as the host machine or node on which another networked entity (such as a service, application, or connection) resides or operates.
  • E. networkProtocolDomain
    Indicates the network protocol or protocol family within which a given communication, service, or interaction operates.
  • F. None of above. chosen

Provenance (4 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_69ef6a5193808190816eb7d0020b2d87 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f66003a3f48190a2ba6da5aafbb5cb completed May 2, 2026, 8:35 p.m.
PD Predicate disambiguation batch_69f65c2198208190a3954086c22cfcbf completed May 2, 2026, 8:18 p.m.
PDg Predicate description generation batch_69f65f75ac608190a62cd6afce14f68e completed May 2, 2026, 8:32 p.m.
Created at: April 27, 2026, 4:23 p.m.