Triple
T8918659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDAP |
E212355
|
entity |
| Predicate | definedInRFC |
P5655
|
FINISHED |
| Object |
RFC 7484
RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
|
E773538
|
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 7484 | Statement: [RDAP, definedInRFC, RFC 7484]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7484 Context triple: [RDAP, definedInRFC, RFC 7484]
-
A.
RFC 7684
RFC 7684 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the earlier OSPFv3 specification defined in RFC 5340.
-
B.
RFC 7483
RFC 7483 is the IETF specification that defines the JSON-based data format and usage for the Registration Data Access Protocol (RDAP) used to query domain and network registration information.
-
C.
RFC 7482
RFC 7482 is the IETF specification that defines the HTTP-based query format and usage for the Registration Data Access Protocol (RDAP).
-
D.
RFC 7480
RFC 7480 is an Internet Engineering Task Force (IETF) standard that specifies the HTTP usage and transport considerations for the Registration Data Access Protocol (RDAP).
-
E.
RFC 7481
RFC 7481 is an IETF standards document that specifies the security services and requirements for the Registration Data Access Protocol (RDAP).
- 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 7484 Triple: [RDAP, definedInRFC, RFC 7484]
Generated description
RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 7484 Target entity description: RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
-
A.
RFC 7684
RFC 7684 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the earlier OSPFv3 specification defined in RFC 5340.
-
B.
RFC 7483
RFC 7483 is the IETF specification that defines the JSON-based data format and usage for the Registration Data Access Protocol (RDAP) used to query domain and network registration information.
-
C.
RFC 7482
RFC 7482 is the IETF specification that defines the HTTP-based query format and usage for the Registration Data Access Protocol (RDAP).
-
D.
RFC 7480
RFC 7480 is an Internet Engineering Task Force (IETF) standard that specifies the HTTP usage and transport considerations for the Registration Data Access Protocol (RDAP).
-
E.
RFC 7481
RFC 7481 is an IETF standards document that specifies the security services and requirements for the Registration Data Access Protocol (RDAP).
- 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_69cfdb83445c819085be0b13517292c9 |
completed | April 3, 2026, 3:23 p.m. |
| NEDg | Description generation | batch_69cfe012b3d48190ba38e8ee3bb0fc8b |
completed | April 3, 2026, 3:43 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cfe060aaec8190af5f7dd8914f5325 |
completed | April 3, 2026, 3:44 p.m. |
Created at: March 30, 2026, 6:56 p.m.