Triple

T23362968
Position Surface form Disambiguated ID Type / Status
Subject P. Matthews E593234 entity
Predicate contributedTo P37 FINISHED
Object RFC 6052 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 6052 | Statement: [P. Matthews, contributedTo, RFC 6052]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 6052
Context triple: [P. Matthews, contributedTo, RFC 6052]
  • A. RFC 6052 chosen
    RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
  • B. RFC 6352
    RFC 6352 is the Internet standards document that specifies the CardDAV protocol for remote access and management of contact data stored on a server.
  • C. RFC 6062
    RFC 6062 is an IETF specification that extends the TURN protocol to support TCP relaying for applications operating across NATs and firewalls.
  • D. RFC 6605
    RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
  • E. RFC 5702
    RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
  • 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_69e25d2593c88190bcdf4a716a94ccb2 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a0aa0ed88190b0198cbfd1bcc59b completed April 29, 2026, 6:09 a.m.
Created at: April 17, 2026, 5:30 p.m.