Triple
T3081743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1122 |
E64273
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1042
RFC 1042 is an early Internet standard that specifies how to encapsulate IP and ARP packets over IEEE 802 local area networks.
|
E325859
|
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 1042 | Statement: [RFC 1122, obsoletes, RFC 1042]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1042 Context triple: [RFC 1122, obsoletes, RFC 1042]
-
A.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
-
B.
RFC 1451
RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
C.
RFC 1048
RFC 1048 is an Internet standards document that specifies the vendor information extensions for the BOOTP protocol, laying groundwork later used by DHCP.
-
D.
RFC 1541
RFC 1541 is an early Internet standards document that originally specified the Dynamic Host Configuration Protocol (DHCP) for automatic IP address assignment before being superseded by RFC 2131.
-
E.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
- 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 1042 Triple: [RFC 1122, obsoletes, RFC 1042]
Generated description
RFC 1042 is an early Internet standard that specifies how to encapsulate IP and ARP packets over IEEE 802 local area networks.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1042 Target entity description: RFC 1042 is an early Internet standard that specifies how to encapsulate IP and ARP packets over IEEE 802 local area networks.
-
A.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
-
B.
RFC 1451
RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
C.
RFC 1048
RFC 1048 is an Internet standards document that specifies the vendor information extensions for the BOOTP protocol, laying groundwork later used by DHCP.
-
D.
RFC 1541
RFC 1541 is an early Internet standards document that originally specified the Dynamic Host Configuration Protocol (DHCP) for automatic IP address assignment before being superseded by RFC 2131.
-
E.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
- 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.