Triple

T2724394
Position Surface form Disambiguated ID Type / Status
Subject RFC 793 E60156 entity
Predicate protocolAcronym P36183 FINISHED
Object TCP E10705 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 | Statement: [RFC 793, protocolAcronym, TCP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TCP
Context triple: [RFC 793, protocolAcronym, TCP]
  • A. Transmission Control Protocol chosen
    Transmission Control Protocol is a core internet communication protocol that provides reliable, ordered, and error-checked delivery of data between applications over IP networks.
  • B. TCP/IP
    TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
  • C. UDP
    UDP (User Datagram Protocol) is a lightweight, connectionless transport-layer protocol used on the Internet for fast, low-overhead data transmission without guaranteed delivery or ordering.
  • D. SCTP
    SCTP (Stream Control Transmission Protocol) is a transport-layer network protocol designed to provide reliable, message-oriented communication with features like multi-streaming and multi-homing, often used for signaling and real-time data transmission.
  • E. RFC 793
    RFC 793 is the foundational Internet standard that defines the Transmission Control Protocol (TCP), specifying how reliable, ordered, and error-checked data transmission works between hosts on an IP network.
  • 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: protocolAcronym
Context triple: [RFC 793, protocolAcronym, TCP]
  • A. protocolName
    Indicates the specific communication or interaction protocol used or associated with an entity or connection.
  • B. protocol
    Indicates that one entity defines or follows a specific set of rules or procedures governing how it interacts or communicates with another entity.
  • C. protocolFullName
    Indicates that one entity is the complete, human-readable name of a protocol associated with another entity.
  • D. abbreviationUsedFor chosen
    Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
  • E. protocolLayer
    Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
  • 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_69ab4b746d248190958e052045c09255 completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdacc0a6881909b64a4d22e1d7690 completed March 7, 2026, 7:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69afb69605308190b5a8078b275791fb completed March 10, 2026, 6:13 a.m.
PD Predicate disambiguation batch_69abd82586f88190a98f60d3247fe2d3 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:55 p.m.