Triple

T22062117
Position Surface form Disambiguated ID Type / Status
Subject RFC 7684 E545178 entity
Predicate abbreviation P43 FINISHED
Object RFC 7684 NE NERFINISHED

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 7684 | Statement: [RFC 7684, abbreviation, RFC 7684]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 7684
Context triple: [RFC 7684, abbreviation, RFC 7684]
  • A. RFC 7684 chosen
    RFC 7684 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the earlier OSPFv3 specification defined in RFC 5340.
  • B. RFC 7484
    RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
  • C. RFC 7664
    RFC 7664 is an IETF standard that specifies the Dragonfly password-authenticated key exchange protocol used to establish secure cryptographic keys based on shared passwords.
  • D. RFC 7674
    RFC 7674 is an Internet standards document that specifies how to use DANE (DNS-Based Authentication of Named Entities) for securing email transport with TLS.
  • E. RFC 7344
    RFC 7344 is an Internet Engineering Task Force (IETF) standard that specifies automated mechanisms for maintaining DNSSEC delegation trust using CDS and related records.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e11e3377c48190890c17407b9527d6 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1285e8c688190b701e417893cc148 completed April 28, 2026, 9:36 p.m.
Created at: April 16, 2026, 8:27 p.m.