Triple
T8918660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDAP |
E212355
|
entity |
| Predicate | definedInRFC |
P5655
|
FINISHED |
| Object |
RFC 8056
RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
|
E766427
|
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 8056 | Statement: [RDAP, definedInRFC, RFC 8056]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8056 Context triple: [RDAP, definedInRFC, RFC 8056]
-
A.
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.
-
B.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
C.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
D.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
E.
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
- 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 8056 Triple: [RDAP, definedInRFC, RFC 8056]
Generated description
RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8056 Target entity description: RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
-
A.
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.
-
B.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
C.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
D.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
E.
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6613639881909090d060f388a865 |
completed | April 1, 2026, 12:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba49d65c8190b9d9908822198cc0 |
completed | April 3, 2026, 1:02 p.m. |
| NEDg | Description generation | batch_69cfbb35869c8190a75ddf6627667623 |
completed | April 3, 2026, 1:05 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cfbb9585688190b3aa3d817bafba51 |
completed | April 3, 2026, 1:07 p.m. |
Created at: March 30, 2026, 6:56 p.m.