Triple

T1631566
Position Surface form Disambiguated ID Type / Status
Subject RFC 854 E35267 entity
Predicate usesUnderlyingProtocolSuite P1215 FINISHED
Object TCP/IP E1063 NE FINISHED

How this triple was built (3 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: TCP/IP | Statement: [RFC 854, usesUnderlyingProtocolSuite, TCP/IP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TCP/IP
Context triple: [RFC 854, usesUnderlyingProtocolSuite, TCP/IP]
  • A. TCP/IP chosen
    TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
  • B. Internet Protocol
    Internet Protocol is the core networking protocol that defines how data packets are addressed and routed across interconnected computer networks, forming the foundation of the modern internet.
  • C. Transmission Control Protocol
    Transmission Control Protocol is a core internet communication protocol that provides reliable, ordered, and error-checked delivery of data between applications over IP networks.
  • D. OSI protocol suite
    The OSI protocol suite is a conceptual networking framework that defines a seven-layer model for how different communication protocols interact to enable data exchange across networks.
  • E. ICMP
    ICMP (Internet Control Message Protocol) is a core network-layer protocol used primarily for sending error messages and operational information, such as in tools like ping and traceroute, within IP networks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesUnderlyingProtocolSuite
Context triple: [RFC 854, usesUnderlyingProtocolSuite, TCP/IP]
  • A. usesProtocolSuite chosen
    Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
  • B. usedInProtocol
    Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
  • C. hasProtocol
    Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
  • D. implementedUnder
    Indicates that an action, policy, or process is carried out within the scope, authority, or framework defined by a particular higher-level plan, rule, or governing entity.
  • E. isSupportedBy
    Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
  • F. None of above.

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_69a886036bc081909ff5de16dbe5e8ea completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9431af5ac8190893133f1ae490142 completed March 5, 2026, 8:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad58d79bc88190bfc62f53dd8e8b90 completed March 8, 2026, 11:09 a.m.
PD Predicate disambiguation batch_69a907c91c888190b6ed295c1a2e0977 completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:28 p.m.