Triple
T8611096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Printing Protocol |
E203914
|
entity |
| Predicate | hasRFC |
P83873
|
FINISHED |
| Object |
RFC 2911
RFC 2911 is the core specification that defines the Internet Printing Protocol (IPP) model, operations, and attributes used for network printing.
|
E745322
|
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 2911 | Statement: [Internet Printing Protocol, hasRFC, RFC 2911]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2911 Context triple: [Internet Printing Protocol, hasRFC, RFC 2911]
-
A.
RFC 2811
RFC 2811 is an Internet standards document that specifies the architecture and operation of Internet Relay Chat (IRC) channel management.
-
B.
RFC 2481
RFC 2481 is an early experimental specification that introduced Explicit Congestion Notification (ECN) for IP and TCP to signal network congestion without packet loss.
-
C.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
D.
RFC 1591
RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
-
E.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
- 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 2911 Triple: [Internet Printing Protocol, hasRFC, RFC 2911]
Generated description
RFC 2911 is the core specification that defines the Internet Printing Protocol (IPP) model, operations, and attributes used for network printing.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2911 Target entity description: RFC 2911 is the core specification that defines the Internet Printing Protocol (IPP) model, operations, and attributes used for network printing.
-
A.
RFC 2811
RFC 2811 is an Internet standards document that specifies the architecture and operation of Internet Relay Chat (IRC) channel management.
-
B.
RFC 2481
RFC 2481 is an early experimental specification that introduced Explicit Congestion Notification (ECN) for IP and TCP to signal network congestion without packet loss.
-
C.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
D.
RFC 1591
RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
-
E.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
- 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_69cea91456a88190a7416b0f1a0327d6 |
completed | April 2, 2026, 5:36 p.m. |
| NEDg | Description generation | batch_69cea9e685388190a4be9d2135dc02d0 |
completed | April 2, 2026, 5:39 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ceaababe2c8190bc47430d33bfdbaa |
completed | April 2, 2026, 5:43 p.m. |
Created at: March 30, 2026, 6:25 p.m.