Triple

T21091613
Position Surface form Disambiguated ID Type / Status
Subject RIP E519651 entity
Predicate definedIn P775 FINISHED
Object RFC 1058 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 1058 | Statement: [RIP, definedIn, RFC 1058]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 1058
Context triple: [RIP, definedIn, RFC 1058]
  • A. 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.
  • B. RFC 1055
    RFC 1055 is an early Internet standard that specifies the Serial Line Internet Protocol (SLIP) for transmitting IP packets over serial connections.
  • C. RFC 1908
    RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
  • D. RFC 1548
    RFC 1548 is an early Internet standards document that originally specified the Point-to-Point Protocol (PPP) for transmitting network-layer datagrams over serial links.
  • E. RFC 1038
    RFC 1038 is an early Internet standards document that specifies experimental extensions to the IP protocol, particularly for security and related options.
  • 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 1058
Target entity description: RFC 1058 is the Internet standard document that specifies the original Routing Information Protocol (RIP) used for distance-vector routing in IP networks.
  • A. 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.
  • B. RFC 1055
    RFC 1055 is an early Internet standard that specifies the Serial Line Internet Protocol (SLIP) for transmitting IP packets over serial connections.
  • C. RFC 1908
    RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
  • D. RFC 1548
    RFC 1548 is an early Internet standards document that originally specified the Point-to-Point Protocol (PPP) for transmitting network-layer datagrams over serial links.
  • E. RFC 1038
    RFC 1038 is an early Internet standards document that specifies experimental extensions to the IP protocol, particularly for security and related options.
  • 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.