Triple

T21264751
Position Surface form Disambiguated ID Type / Status
Subject RFC 3948 E524096 entity
Predicate relatedToRFC P9936 FINISHED
Object RFC 2401 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 2401 | Statement: [RFC 3948, relatedToRFC, RFC 2401]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 2401
Context triple: [RFC 3948, relatedToRFC, RFC 2401]
  • A. RFC 2401 chosen
    RFC 2401 is an Internet Engineering Task Force (IETF) standard that defines the Security Architecture for the Internet Protocol, forming the core specification for IPsec.
  • B. RFC 2402
    RFC 2402 is an Internet standards document that defines the IP Authentication Header (AH) protocol used to provide connectionless integrity, data origin authentication, and optional anti-replay protection for IP packets.
  • C. RFC 2408
    RFC 2408 is an Internet standards document that defines the Internet Security Association and Key Management Protocol (ISAKMP) used as a framework for key exchange and security association management in IPsec.
  • D. RFC 4301
    RFC 4301 is an IETF standard that defines the Security Architecture for IP, including the core framework and mechanisms for IPsec-based network security.
  • E. RFC 2409
    RFC 2409 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange (IKE) protocol used to establish secure, authenticated keying material for IPsec.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relatedToRFC
Context triple: [RFC 3948, relatedToRFC, RFC 2401]
  • A. relatedRFC chosen
    Indicates that one resource or specification is connected or associated with another through a shared or relevant RFC (Request for Comments) document.
  • B. relationToIETF
    Indicates the nature of an entity’s connection or involvement with the Internet Engineering Task Force (IETF), such as affiliation, participation, or oversight.
  • C. relatedTo
    Indicates a general, non-specific relationship or association exists between two entities.
  • D. hasRFC
    Indicates that an entity is associated with, described by, or defined in a specific RFC (Request for Comments) document.
  • E. relatedToTerm
    Indicates a general, non-specific relationship or association between one term and another.
  • F. None of above.

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_69e0b5156d7881909bd4f83676590715 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e735ea74e0819099d724de95996c90 completed April 21, 2026, 8:31 a.m.
PD Predicate disambiguation batch_69e5f61239708190ab7b3c83ae848a0d completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 4 p.m.