Triple
T3081733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1122 |
E64273
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1022
RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
|
E325857
|
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 1022 | Statement: [RFC 1122, obsoletes, RFC 1022]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1022 Context triple: [RFC 1122, obsoletes, RFC 1022]
-
A.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
B.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
-
C.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
D.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
-
E.
RFC 2821
RFC 2821 is an earlier Internet standard that defined the Simple Mail Transfer Protocol (SMTP) for email transmission before being superseded by RFC 5321.
- 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 1022 Triple: [RFC 1122, obsoletes, RFC 1022]
Generated description
RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1022 Target entity description: RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
-
A.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
B.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
-
C.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
D.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
-
E.
RFC 2821
RFC 2821 is an earlier Internet standard that defined the Simple Mail Transfer Protocol (SMTP) for email transmission before being superseded by RFC 5321.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1e70b9081908c801d084a6ae992 |
completed | March 8, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1f89847e48190b82849701e119758 |
completed | March 11, 2026, 11:19 p.m. |
| NEDg | Description generation | batch_69b1f9608e88819098f4044e54e0d908 |
completed | March 11, 2026, 11:23 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b1fe3c8f408190988e7c7e3a51057e |
completed | March 11, 2026, 11:43 p.m. |
Created at: March 8, 2026, 3:03 p.m.