Triple

T21091671
Position Surface form Disambiguated ID Type / Status
Subject Routing Information Protocol E519652 entity
Predicate standardizedIn P7508 FINISHED
Object RFC 1723 NE NERFINISHED

How this triple was built (3 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 1723 | Statement: [Routing Information Protocol, standardizedIn, RFC 1723]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 1723
Context triple: [Routing Information Protocol, standardizedIn, RFC 1723]
  • A. RFC 733
    RFC 733 is an early Internet standard that defined the format for ARPA network text messages, serving as a foundational specification for modern email message structure.
  • B. RFC 1442
    RFC 1442 is an early Internet standards document that defined the Structure of Management Information (SMI) for version 2 of the Simple Network Management Protocol (SNMPv2).
  • C. RFC 1331
    RFC 1331 is an early specification in the Point-to-Point Protocol (PPP) standards series that was later superseded by RFC 1661.
  • 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 1441
    RFC 1441 is an early standards-track document in the Simple Network Management Protocol (SNMP) framework that was later superseded by RFC 1901 as the protocol evolved.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 1723
Target entity description: RFC 1723 is an Internet Engineering Task Force (IETF) standards document that specifies version 2 of the Routing Information Protocol (RIP), a distance-vector routing protocol used in IP networks.
  • A. RFC 733
    RFC 733 is an early Internet standard that defined the format for ARPA network text messages, serving as a foundational specification for modern email message structure.
  • B. RFC 1442
    RFC 1442 is an early Internet standards document that defined the Structure of Management Information (SMI) for version 2 of the Simple Network Management Protocol (SNMPv2).
  • C. RFC 1331
    RFC 1331 is an early specification in the Point-to-Point Protocol (PPP) standards series that was later superseded by RFC 1661.
  • 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 1441
    RFC 1441 is an early standards-track document in the Simple Network Management Protocol (SNMP) framework that was later superseded by RFC 1901 as the protocol evolved.
  • F. None of above. chosen

Provenance (2 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_69e0b507dd9081908fb8bfcbef4c8b46 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7094f6ebc8190a90b014755a9d4a6 completed April 21, 2026, 5:21 a.m.
Created at: April 16, 2026, 2:51 p.m.