Triple

T9944655
Position Surface form Disambiguated ID Type / Status
Subject RFC 862 E194171 entity
Predicate similarTo P4460 FINISHED
Object RFC 863
RFC 863 is an Internet standard that specifies the Discard Protocol, a simple service that accepts and then silently throws away any data sent to it, primarily used for testing and measurement.
 E832857 NE FINISHED

How this triple was built (4 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 863 | Statement: [RFC 862, similarTo, RFC 863]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 863
Context triple: [RFC 862, similarTo, RFC 863]
  • A. RFC 862
    RFC 862 is an Internet standard that specifies the Echo Protocol, a simple service used primarily for testing and measurement by sending data to a server that returns it unchanged.
  • B. RFC 867
    RFC 867 is an early Internet standard that defines the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
  • C. RFC 866
    RFC 866 is an early Internet standard that specifies the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
  • D. RFC 883
    RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
  • E. RFC 860
    RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 863
Triple: [RFC 862, similarTo, RFC 863]
Generated description
RFC 863 is an Internet standard that specifies the Discard Protocol, a simple service that accepts and then silently throws away any data sent to it, primarily used for testing and measurement.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 863
Target entity description: RFC 863 is an Internet standard that specifies the Discard Protocol, a simple service that accepts and then silently throws away any data sent to it, primarily used for testing and measurement.
  • A. RFC 862
    RFC 862 is an Internet standard that specifies the Echo Protocol, a simple service used primarily for testing and measurement by sending data to a server that returns it unchanged.
  • B. RFC 867
    RFC 867 is an early Internet standard that defines the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
  • C. RFC 866
    RFC 866 is an early Internet standard that specifies the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
  • D. RFC 883
    RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
  • E. RFC 860
    RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
  • F. None of above. chosen

Provenance (5 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_69ca82e409348190a393777356b80a2a completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb61561848190aba7250f3b3c4ed5 completed April 2, 2026, 12:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69d23d5c6fdc81909b44d0b321201222 completed April 5, 2026, 10:45 a.m.
NEDg Description generation batch_69d23eb1c1f481908404225dcccd0697 completed April 5, 2026, 10:51 a.m.
NED2 Entity disambiguation (via description) batch_69d242aea6a08190a73a836e59865c35 completed April 5, 2026, 11:08 a.m.
Created at: March 30, 2026, 8:45 p.m.