Triple

T3081747
Position Surface form Disambiguated ID Type / Status
Subject RFC 1122 E64273 entity
Predicate obsoletes P101 FINISHED
Object RFC 1108
RFC 1108 is an early Internet standards document that specifies security options for the Internet Protocol (IP), particularly for use in military and other high-security environments.
 E336834 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 1108 | Statement: [RFC 1122, obsoletes, RFC 1108]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 1108
Context triple: [RFC 1122, obsoletes, RFC 1108]
  • A. RFC 1908
    RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
  • B. RFC 1668
    RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
  • C. RFC 1195
    RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
  • D. RFC 1448
    RFC 1448 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) before being superseded by later revisions such as RFC 1905.
  • E. RFC 1048
    RFC 1048 is an Internet standards document that specifies the vendor information extensions for the BOOTP protocol, laying groundwork later used by DHCP.
  • 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 1108
Triple: [RFC 1122, obsoletes, RFC 1108]
Generated description
RFC 1108 is an early Internet standards document that specifies security options for the Internet Protocol (IP), particularly for use in military and other high-security environments.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 1108
Target entity description: RFC 1108 is an early Internet standards document that specifies security options for the Internet Protocol (IP), particularly for use in military and other high-security environments.
  • A. RFC 1908
    RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
  • B. RFC 1668
    RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
  • C. RFC 1195
    RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
  • D. RFC 1448
    RFC 1448 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) before being superseded by later revisions such as RFC 1905.
  • E. RFC 1048
    RFC 1048 is an Internet standards document that specifies the vendor information extensions for the BOOTP protocol, laying groundwork later used by DHCP.
  • 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_69ad857bb4c88190a4cf27893fcabed8 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada1e70b9081908c801d084a6ae992 completed March 8, 2026, 4:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69b261eb2e708190b192574d3f5862e6 completed March 12, 2026, 6:49 a.m.
NEDg Description generation batch_69b2638b3b2881909563356ea8a9611c completed March 12, 2026, 6:56 a.m.
NED2 Entity disambiguation (via description) batch_69b264fb42e4819084c289235f33b654 completed March 12, 2026, 7:02 a.m.
Created at: March 8, 2026, 3:03 p.m.