Triple

T14001436
Position Surface form Disambiguated ID Type / Status
Subject RFC 1108 E336834 entity
Predicate obsoletedBy P101 FINISHED
Object RFC 4301 E522219 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 4301 | Statement: [RFC 1108, obsoletedBy, RFC 4301]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 4301
Context triple: [RFC 1108, obsoletedBy, RFC 4301]
  • A. RFC 4301 chosen
    RFC 4301 is an IETF standard that defines the Security Architecture for IP, including the core framework and mechanisms for IPsec-based network security.
  • B. RFC 2401
    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.
  • C. 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.
  • D. 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.
  • E. RFC 3412
    RFC 3412 is an Internet standard that specifies the message processing and dispatching procedures for the Simple Network Management Protocol (SNMP) within the SNMPv3 framework.
  • 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_69d81c645c5c8190b1fd16a285a1b78a completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2ed06a50819093ddc64f55050689 completed April 14, 2026, 12:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbaca180988190bbfc93bd708688d6 completed May 6, 2026, 9:03 p.m.
Created at: April 9, 2026, 10:19 p.m.