Triple
T8692851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5011 |
E206332
|
entity |
| Predicate | identifier |
P3732
|
FINISHED |
| Object | RFC 5011 |
E206332
|
NE FINISHED |
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 5011 | Statement: [RFC 5011, identifier, RFC 5011]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5011 Context triple: [RFC 5011, identifier, RFC 5011]
-
A.
RFC 5011
chosen
RFC 5011 is an Internet standard that specifies automated trust anchor rollover mechanisms for DNSSEC to simplify and secure key management in the Domain Name System.
-
B.
RFC 3711
RFC 3711 is the IETF specification that defines the Secure Real-time Transport Protocol (SRTP), a framework for providing encryption, message authentication, and integrity for real-time audio and video over IP networks.
-
C.
RFC 5661
RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
-
D.
RFC 8011
RFC 8011 is the IETF specification that defines the core model, semantics, and operations of the Internet Printing Protocol (IPP) used for network printing.
-
E.
RFC 5751
RFC 5751 is the Internet standards document that specifies the Secure/Multipurpose Internet Mail Extensions (S/MIME) protocol for secure email communication.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5825385081908dee42cba8e98392 |
completed | March 31, 2026, 11:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cef3ea2ba08190b8046e703ba7d2d8 |
completed | April 2, 2026, 10:55 p.m. |
Created at: March 30, 2026, 6:33 p.m.