Triple

T22027172
Position Surface form Disambiguated ID Type / Status
Subject IETF BEHAVE working group E543996 entity
Predicate produced P490 FINISHED
Object RFC 6269 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 6269 | Statement: [IETF BEHAVE working group, produced, RFC 6269]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 6269
Context triple: [IETF BEHAVE working group, produced, RFC 6269]
  • A. RFC 6189
    RFC 6189 is the Internet Engineering Task Force (IETF) standard that defines the ZRTP protocol for secure key agreement in Voice over IP communications.
  • B. RFC 6409
    RFC 6409 is an Internet standards document that originally defined the Message Submission protocol for email (port 587), later superseded by RFC 8314.
  • C. RFC 6089
    RFC 6089 is an IETF specification that defines localized routing extensions for Proxy Mobile IPv6 to optimize traffic paths and reduce latency in mobile networks.
  • D. RFC 6066
    RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
  • E. RFC 6096
    RFC 6096 is an Internet Engineering Task Force (IETF) standards document that refines and updates the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
  • 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 6269
Target entity description: RFC 6269 is an Internet Engineering Task Force document that analyzes the implications and issues of large-scale NAT (Network Address Translation) deployments on Internet architecture and applications.
  • A. RFC 6189
    RFC 6189 is the Internet Engineering Task Force (IETF) standard that defines the ZRTP protocol for secure key agreement in Voice over IP communications.
  • B. RFC 6409
    RFC 6409 is an Internet standards document that originally defined the Message Submission protocol for email (port 587), later superseded by RFC 8314.
  • C. RFC 6089
    RFC 6089 is an IETF specification that defines localized routing extensions for Proxy Mobile IPv6 to optimize traffic paths and reduce latency in mobile networks.
  • D. RFC 6066
    RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
  • E. RFC 6096
    RFC 6096 is an Internet Engineering Task Force (IETF) standards document that refines and updates the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
  • 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.