Triple

T4402475
Position Surface form Disambiguated ID Type / Status
Subject X.25 E93647 entity
Predicate replacedBy P101 FINISHED
Object TCP/IP E1063 NE 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: TCP/IP | Statement: [X.25, replacedBy, TCP/IP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TCP/IP
Context triple: [X.25, replacedBy, 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.

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_69b345158c748190a2c040fce2da9980 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b352d08a0c8190ac6c125df40eca75 completed March 12, 2026, 11:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5f5fc9f508190a31adb0758555dfa completed March 14, 2026, 11:57 p.m.
Created at: March 12, 2026, 11:28 p.m.