Triple

T22027171
Position Surface form Disambiguated ID Type / Status
Subject IETF BEHAVE working group E543996 entity
Predicate produced P490 FINISHED
Object RFC 6144 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 6144 | Statement: [IETF BEHAVE working group, produced, RFC 6144]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 6144
Context triple: [IETF BEHAVE working group, produced, RFC 6144]
  • A. RFC 7144
    RFC 7144 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original iSCSI protocol specification defined in RFC 3720.
  • B. RFC 6145
    RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
  • C. RFC 4844
    RFC 4844 is an Internet Engineering Task Force (IETF) document that defines the framework and responsibilities of the RFC Editor function within the RFC Series.
  • D. RFC 5214
    RFC 5214 is an IETF standard that specifies the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) for transmitting IPv6 packets over IPv4 networks.
  • E. RFC 4306
    RFC 4306 is the original specification of the Internet Key Exchange Protocol version 2 (IKEv2), defining mechanisms for setting up secure IPsec-based VPN connections.
  • 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 6144
Target entity description: RFC 6144 is an Internet Engineering Task Force (IETF) standard that specifies framework and requirements for IPv4/IPv6 translation mechanisms used in network address translation (NAT) environments.
  • A. RFC 7144
    RFC 7144 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original iSCSI protocol specification defined in RFC 3720.
  • B. RFC 6145
    RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
  • C. RFC 4844
    RFC 4844 is an Internet Engineering Task Force (IETF) document that defines the framework and responsibilities of the RFC Editor function within the RFC Series.
  • D. RFC 5214
    RFC 5214 is an IETF standard that specifies the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) for transmitting IPv6 packets over IPv4 networks.
  • E. RFC 4306
    RFC 4306 is the original specification of the Internet Key Exchange Protocol version 2 (IKEv2), defining mechanisms for setting up secure IPsec-based VPN connections.
  • 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.