Triple

T1866632
Position Surface form Disambiguated ID Type / Status
Subject RFC 792 E34935 entity
Predicate relatedTo P37 FINISHED
Object RFC 791 E9801 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: RFC 791 | Statement: [RFC 792, relatedTo, RFC 791]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 791
Context triple: [RFC 792, relatedTo, RFC 791]
  • A. RFC 791 chosen
    RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
  • B. RFC 792
    RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
  • C. 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.
  • D. RFC 877
    RFC 877 is an early Internet standards document that specifies the standard for Internet Control Message Protocol (ICMP) echo messages used for network diagnostics such as the "ping" utility.
  • E. RFC 783
    RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
  • 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_69a88600b2f88190bc09303e68ab517e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abb0b5978c81909390f2cbd716ccaf completed March 7, 2026, 4:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69add1d8dd8881909189029a047bc2b4 completed March 8, 2026, 7:45 p.m.
Created at: March 4, 2026, 7:34 p.m.