Triple
T13849347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1055 |
E332892
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 1144
RFC 1144 is an Internet standard that specifies a method for compressing TCP/IP headers over low-speed serial links to improve network efficiency.
|
E1065810
|
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 1144 | Statement: [RFC 1055, obsoletedBy, RFC 1144]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1144 Context triple: [RFC 1055, obsoletedBy, RFC 1144]
-
A.
RFC 1444
RFC 1444 is an Internet standards document that defines the SNMPv2 MIB for managing SNMP entities in network management systems.
-
B.
RFC 1141
RFC 1141 is an Internet standard document that revises and replaces earlier guidance on computing the Internet checksum used in IP networking.
-
C.
RFC 1449
RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
D.
RFC 2144
RFC 2144 is an Internet standards document that specifies the CAST-128 (CAST5) symmetric-key block cipher for use in cryptographic applications.
-
E.
RFC 1448
RFC 1448 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) before being superseded by later revisions such as RFC 1905.
- 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 1144 Triple: [RFC 1055, obsoletedBy, RFC 1144]
Generated description
RFC 1144 is an Internet standard that specifies a method for compressing TCP/IP headers over low-speed serial links to improve network efficiency.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1144 Target entity description: RFC 1144 is an Internet standard that specifies a method for compressing TCP/IP headers over low-speed serial links to improve network efficiency.
-
A.
RFC 1444
RFC 1444 is an Internet standards document that defines the SNMPv2 MIB for managing SNMP entities in network management systems.
-
B.
RFC 1141
RFC 1141 is an Internet standard document that revises and replaces earlier guidance on computing the Internet checksum used in IP networking.
-
C.
RFC 1449
RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
D.
RFC 2144
RFC 2144 is an Internet standards document that specifies the CAST-128 (CAST5) symmetric-key block cipher for use in cryptographic applications.
-
E.
RFC 1448
RFC 1448 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) before being superseded by later revisions such as RFC 1905.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02d8fb788190baef7537be2baecb |
completed | April 14, 2026, 9:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c0f35ba48190b8b071679251233f |
completed | May 3, 2026, 9:41 p.m. |
| NEDg | Description generation | batch_69f7c23410dc8190972245cecfa85871 |
completed | May 3, 2026, 9:46 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f7c3031a0c8190ad30d59fe1f2322e |
completed | May 3, 2026, 9:49 p.m. |
Created at: April 9, 2026, 10:14 p.m.