Triple

T19351972
Position Surface form Disambiguated ID Type / Status
Subject airserv-ng E484044 entity
Predicate supportsProtocol P203 FINISHED
Object TCP NE NERFINISHED

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: TCP | Statement: [airserv-ng, supportsProtocol, TCP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TCP
Context triple: [airserv-ng, supportsProtocol, 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. TCP Tahoe
    TCP Tahoe is an early implementation of the Transmission Control Protocol that introduced foundational congestion control algorithms such as slow start, congestion avoidance, and fast retransmit.
  • D. TCP Reno
    TCP Reno is a widely used variant of the Transmission Control Protocol that introduced key congestion control mechanisms such as fast retransmit and fast recovery to improve Internet performance and stability.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d244f8819080eb1f3491300db2 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e61905b16881909ab0e932bb9a0cda completed April 20, 2026, 12:16 p.m.
Created at: April 10, 2026, 1:34 p.m.