Triple
T13953574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1072 |
E335595
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 1323
RFC 1323 is an Internet standards document that defines TCP extensions for high performance over large bandwidth-delay product networks, including window scaling and timestamps.
|
E1071267
|
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 1323 | Statement: [RFC 1072, obsoletedBy, RFC 1323]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1323 Context triple: [RFC 1072, obsoletedBy, RFC 1323]
-
A.
RFC 1331
RFC 1331 is an early specification in the Point-to-Point Protocol (PPP) standards series that was later superseded by RFC 1661.
-
B.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
C.
RFC 2623
RFC 2623 was an early Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4250.
-
D.
RFC 1349
RFC 1349 is an older Internet standard that originally defined the Type of Service (TOS) field in the IPv4 header before being superseded by later quality-of-service specifications.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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 1323 Triple: [RFC 1072, obsoletedBy, RFC 1323]
Generated description
RFC 1323 is an Internet standards document that defines TCP extensions for high performance over large bandwidth-delay product networks, including window scaling and timestamps.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1323 Target entity description: RFC 1323 is an Internet standards document that defines TCP extensions for high performance over large bandwidth-delay product networks, including window scaling and timestamps.
-
A.
RFC 1331
RFC 1331 is an early specification in the Point-to-Point Protocol (PPP) standards series that was later superseded by RFC 1661.
-
B.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
C.
RFC 2623
RFC 2623 was an early Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4250.
-
D.
RFC 1349
RFC 1349 is an older Internet standard that originally defined the Type of Service (TOS) field in the IPv4 header before being superseded by later quality-of-service specifications.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e146720819085d0f5eae558b7a4 |
completed | April 14, 2026, 12:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fba1d0735c81909ec0eab090af08a1 |
completed | May 6, 2026, 8:17 p.m. |
| NEDg | Description generation | batch_69fba5646cb48190acd932f6fbd6fe62 |
completed | May 6, 2026, 8:32 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fba6525d0c8190a1ab15881030c11c |
completed | May 6, 2026, 8:36 p.m. |
Created at: April 9, 2026, 10:17 p.m.