Triple
T8513110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8551 |
E201504
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object |
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
|
E740115
|
NE FINISHED |
How this triple was built (4 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 8552 | Statement: [RFC 8551, relatedTo, RFC 8552]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8552 Context triple: [RFC 8551, relatedTo, RFC 8552]
-
A.
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.
-
B.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
C.
RFC 8550
RFC 8550 is an Internet standards document that specifies the use of the Online Certificate Status Protocol (OCSP) for validating the status of digital certificates in public key infrastructures.
-
D.
RFC 6052
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.
-
E.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 8552 Triple: [RFC 8551, relatedTo, RFC 8552]
Generated description
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8552 Target entity description: RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
-
A.
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.
-
B.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
C.
RFC 8550
RFC 8550 is an Internet standards document that specifies the use of the Online Certificate Status Protocol (OCSP) for validating the status of digital certificates in public key infrastructures.
-
D.
RFC 6052
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.
-
E.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
- F. None of above. chosen
Provenance (5 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_69ce6d2eef208190b505a64d01f656f4 |
completed | April 2, 2026, 1:20 p.m. |
| NEDg | Description generation | batch_69ce6e69213c8190add7eb9cc74b1a33 |
completed | April 2, 2026, 1:26 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ce6f28ae6481909a8a13613f3eb5e0 |
completed | April 2, 2026, 1:29 p.m. |
Created at: March 30, 2026, 6:15 p.m.