Triple
T8513081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8551 |
E201504
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 5751 |
E197861
|
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 5751 | Statement: [RFC 8551, obsoletes, RFC 5751]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5751 Context triple: [RFC 8551, obsoletes, RFC 5751]
-
A.
RFC 5751
chosen
RFC 5751 is the Internet standards document that specifies the Secure/Multipurpose Internet Mail Extensions (S/MIME) protocol for secure email communication.
-
B.
RFC 8551
RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
-
C.
RFC 5741
RFC 5741 is an Internet Engineering Task Force (IETF) document that defines the structure, responsibilities, and processes governing the IETF document publication streams.
-
D.
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.
-
E.
RFC 5721
RFC 5721 was an Internet standards document that defined an earlier approach to email-related functionality before being superseded by RFC 6856.
- 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe60cdfcc819081a9be1229378ba0 |
completed | March 31, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4e4e64f481908ddf99570fe59332 |
completed | April 2, 2026, 11:09 a.m. |
Created at: March 30, 2026, 6:15 p.m.