Triple

T22027173
Position Surface form Disambiguated ID Type / Status
Subject IETF BEHAVE working group E543996 entity
Predicate produced P490 FINISHED
Object RFC 6888 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 6888 | Statement: [IETF BEHAVE working group, produced, RFC 6888]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 6888
Context triple: [IETF BEHAVE working group, produced, RFC 6888]
  • A. RFC 7888
    RFC 7888 is an Internet Engineering Task Force (IETF) standards document that refines and updates email-related protocols originally defined in RFC 6856.
  • B. RFC 6668
    RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
  • C. RFC 6668
    RFC 6668 is an Internet Engineering Task Force (IETF) standard that specifies the use of SHA-2 data integrity verification algorithms within the Secure Shell (SSH) protocol.
  • D. RFC 6698
    RFC 6698 is the Internet standard that specifies the DNS-Based Authentication of Named Entities (DANE) protocol, which uses DNSSEC to associate TLS certificates with domain names.
  • E. RFC 7868
    RFC 7868 is the IETF specification that documents and standardizes the Enhanced Interior Gateway Routing Protocol (EIGRP) as an informational routing protocol.
  • 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 6888
Target entity description: RFC 6888 is an Internet Engineering Task Force (IETF) standard that specifies requirements and behavior for Carrier-Grade NAT (CGN) devices used by service providers to share IPv4 addresses among multiple customers.
  • A. RFC 7888
    RFC 7888 is an Internet Engineering Task Force (IETF) standards document that refines and updates email-related protocols originally defined in RFC 6856.
  • B. RFC 6668
    RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
  • C. RFC 6668
    RFC 6668 is an Internet Engineering Task Force (IETF) standard that specifies the use of SHA-2 data integrity verification algorithms within the Secure Shell (SSH) protocol.
  • D. RFC 6698
    RFC 6698 is the Internet standard that specifies the DNS-Based Authentication of Named Entities (DANE) protocol, which uses DNSSEC to associate TLS certificates with domain names.
  • E. RFC 7868
    RFC 7868 is the IETF specification that documents and standardizes the Enhanced Interior Gateway Routing Protocol (EIGRP) as an informational routing protocol.
  • 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_69e11e2e8ea4819084210fe06d3a1b8d completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127ccc2ec8190a94d69530d00c06c completed April 28, 2026, 9:34 p.m.
Created at: April 16, 2026, 8:24 p.m.