Triple
T8513109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8551 |
E201504
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object |
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.
|
E738663
|
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 8550 | Statement: [RFC 8551, relatedTo, RFC 8550]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8550 Context triple: [RFC 8551, relatedTo, RFC 8550]
-
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 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.
-
C.
RFC 8536
RFC 8536 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier specifications to define the modern format and handling of time zone data in the Internet ecosystem.
-
D.
RFC 9250
RFC 9250 is an IETF standard that specifies how to run the Domain Name System (DNS) protocol over the QUIC transport for improved performance and privacy.
-
E.
RFC 5905
RFC 5905 is the Internet standard specification that defines version 4 of the Network Time Protocol (NTP) for synchronizing clocks over packet-switched, variable-latency data networks.
- 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 8550 Triple: [RFC 8551, relatedTo, RFC 8550]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8550 Target entity description: 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.
-
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 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.
-
C.
RFC 8536
RFC 8536 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier specifications to define the modern format and handling of time zone data in the Internet ecosystem.
-
D.
RFC 9250
RFC 9250 is an IETF standard that specifies how to run the Domain Name System (DNS) protocol over the QUIC transport for improved performance and privacy.
-
E.
RFC 5905
RFC 5905 is the Internet standard specification that defines version 4 of the Network Time Protocol (NTP) for synchronizing clocks over packet-switched, variable-latency data networks.
- 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_69ce4e4e64f481908ddf99570fe59332 |
completed | April 2, 2026, 11:09 a.m. |
| NEDg | Description generation | batch_69ce4ff9792c81908d76141904a170bc |
completed | April 2, 2026, 11:16 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ce50acae5881908f1d2c0e21dd7f1d |
completed | April 2, 2026, 11:19 a.m. |
Created at: March 30, 2026, 6:15 p.m.