Triple

T9930754
Position Surface form Disambiguated ID Type / Status
Subject RFC 973 E192641 entity
Predicate updates P4061 FINISHED
Object RFC 883 E37188 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 883 | Statement: [RFC 973, updates, RFC 883]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 883
Context triple: [RFC 973, updates, RFC 883]
  • A. RFC 883 chosen
    RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
  • B. RFC 882
    RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
  • C. 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.
  • D. RFC 923
    RFC 923 is an Internet standards document that superseded RFC 870 by updating and refining specifications related to early Internet protocol operations.
  • E. 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.
  • 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_69ca82dd978c8190947124ab0d3315ac completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb5b4196881909a004091a4203c45 completed April 2, 2026, 12:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69d228cab0fc81908ff5fad6916c1bab completed April 5, 2026, 9:18 a.m.
Created at: March 30, 2026, 8:43 p.m.