Triple
T8611103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Printing Protocol |
E203914
|
entity |
| Predicate | hasRFC |
P83873
|
FINISHED |
| Object |
RFC 8011
RFC 8011 is the IETF specification that defines the core model, semantics, and operations of the Internet Printing Protocol (IPP) used for network printing.
|
E746696
|
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 8011 | Statement: [Internet Printing Protocol, hasRFC, RFC 8011]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8011 Context triple: [Internet Printing Protocol, hasRFC, RFC 8011]
-
A.
RFC 8010
RFC 8010 is an IETF specification that defines the Internet Printing Protocol (IPP) model and semantics for network printing.
-
B.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
-
C.
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.
-
D.
RFC 5011
RFC 5011 is an Internet standard that specifies automated trust anchor rollover mechanisms for DNSSEC to simplify and secure key management in the Domain Name System.
-
E.
RFC 6081
RFC 6081 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve IPv6 connectivity across IPv4 networks with NAT.
- 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 8011 Triple: [Internet Printing Protocol, hasRFC, RFC 8011]
Generated description
RFC 8011 is the IETF specification that defines the core model, semantics, and operations of the Internet Printing Protocol (IPP) used for network printing.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8011 Target entity description: RFC 8011 is the IETF specification that defines the core model, semantics, and operations of the Internet Printing Protocol (IPP) used for network printing.
-
A.
RFC 8010
RFC 8010 is an IETF specification that defines the Internet Printing Protocol (IPP) model and semantics for network printing.
-
B.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
-
C.
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.
-
D.
RFC 5011
RFC 5011 is an Internet standard that specifies automated trust anchor rollover mechanisms for DNSSEC to simplify and secure key management in the Domain Name System.
-
E.
RFC 6081
RFC 6081 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve IPv6 connectivity across IPv4 networks with NAT.
- 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.