Triple
T21091615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIP |
E519651
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object |
RFC 2080
RFC 2080 is the Internet standard that specifies the RIPng (Routing Information Protocol next generation) protocol for use with IPv6 networks.
|
E1466333
|
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 2080 | Statement: [RIP, definedIn, RFC 2080]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2080 Context triple: [RIP, definedIn, RFC 2080]
-
A.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
-
D.
RFC 3380
RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
-
E.
RFC 5080
RFC 5080 is an IETF standards-track document that provides clarifications and implementation guidelines for the Remote Authentication Dial-In User Service (RADIUS) protocol and related extensions.
- 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 2080 Triple: [RIP, definedIn, RFC 2080]
Generated description
RFC 2080 is the Internet standard that specifies the RIPng (Routing Information Protocol next generation) protocol for use with IPv6 networks.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2080 Target entity description: RFC 2080 is the Internet standard that specifies the RIPng (Routing Information Protocol next generation) protocol for use with IPv6 networks.
-
A.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
-
D.
RFC 3380
RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
-
E.
RFC 5080
RFC 5080 is an IETF standards-track document that provides clarifications and implementation guidelines for the Remote Authentication Dial-In User Service (RADIUS) protocol and related extensions.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094f6ebc8190a90b014755a9d4a6 |
completed | April 21, 2026, 5:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a095a5a70c88190812a7ec9efa8fa42 |
completed | May 17, 2026, 6:04 a.m. |
| NEDg | Description generation | batch_6a095c017bec81909fd6c73a0fb677df |
completed | May 17, 2026, 6:11 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a095cee4c308190a08844f285231ff9 |
completed | May 17, 2026, 6:15 a.m. |
Created at: April 16, 2026, 2:51 p.m.