Triple
T8611100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Printing Protocol |
E203914
|
entity |
| Predicate | hasRFC |
P83873
|
FINISHED |
| Object |
RFC 3996
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
|
E746695
|
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 3996 | Statement: [Internet Printing Protocol, hasRFC, RFC 3996]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3996 Context triple: [Internet Printing Protocol, hasRFC, RFC 3996]
-
A.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
B.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
C.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 3629
RFC 3629 is the Internet standard that defines the UTF-8 character encoding for representing Unicode/ISO/IEC 10646 characters in a byte-oriented format.
- 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 3996 Triple: [Internet Printing Protocol, hasRFC, RFC 3996]
Generated description
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3996 Target entity description: RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
-
A.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
B.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
C.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 3629
RFC 3629 is the Internet standard that defines the UTF-8 character encoding for representing Unicode/ISO/IEC 10646 characters in a byte-oriented format.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc5c2d852081908901f5d2a47035b0 |
completed | March 31, 2026, 11:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cebbc1d8a08190bbcf7c4cef0fe04d |
completed | April 2, 2026, 6:56 p.m. |
| NEDg | Description generation | batch_69cebcc22d208190801b4ec58614dfcb |
completed | April 2, 2026, 7 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cebdf3f288819088d83165c741d092 |
completed | April 2, 2026, 7:05 p.m. |
Created at: March 30, 2026, 6:25 p.m.