Triple
T10243966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5751 |
E197861
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 8551 |
E201504
|
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 8551 | Statement: [RFC 5751, obsoletedBy, RFC 8551]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8551 Context triple: [RFC 5751, obsoletedBy, RFC 8551]
-
A.
RFC 8551
chosen
RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
-
B.
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
-
C.
RFC 5751
RFC 5751 is the Internet standards document that specifies the Secure/Multipurpose Internet Mail Extensions (S/MIME) protocol for secure email communication.
-
D.
RFC 5155
RFC 5155 is an Internet standards document that specifies the NSEC3 extension to DNSSEC, enhancing DNS security by providing authenticated denial of existence while mitigating zone enumeration.
-
E.
RFC 8881
RFC 8881 is the Internet Engineering Task Force (IETF) standard that specifies the Network File System (NFS) version 4.1 protocol, updating and replacing the original NFSv4 specification.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d22a76188190a73df23bfb08eb3d |
completed | April 7, 2026, 9:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71cb24d088190848d2fb1fffe4c48 |
completed | April 9, 2026, 3:27 a.m. |
Created at: April 6, 2026, 11:26 a.m.