Triple
T9731962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1654 |
E235766
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1548
RFC 1548 is an early Internet standards document that originally specified the Point-to-Point Protocol (PPP) for transmitting network-layer datagrams over serial links.
|
E816307
|
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 1548 | Statement: [RFC 1654, obsoletes, RFC 1548]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1548 Context triple: [RFC 1654, obsoletes, RFC 1548]
-
A.
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.
-
B.
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.
-
C.
RFC 1542
RFC 1542 is an Internet standards document that updates and clarifies the behavior of BOOTP relay agents and related mechanisms for IP networks.
-
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 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
- 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 1548 Triple: [RFC 1654, obsoletes, RFC 1548]
Generated description
RFC 1548 is an early Internet standards document that originally specified the Point-to-Point Protocol (PPP) for transmitting network-layer datagrams over serial links.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1548 Target entity description: RFC 1548 is an early Internet standards document that originally specified the Point-to-Point Protocol (PPP) for transmitting network-layer datagrams over serial links.
-
A.
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.
-
B.
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.
-
C.
RFC 1542
RFC 1542 is an Internet standards document that updates and clarifies the behavior of BOOTP relay agents and related mechanisms for IP networks.
-
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 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eb3d6e4819090b3c7fb92550c57 |
completed | April 1, 2026, 10:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19fbbba2081909a15725a68423162 |
completed | April 4, 2026, 11:33 p.m. |
| NEDg | Description generation | batch_69d1a065ce008190985b792302daa7cb |
completed | April 4, 2026, 11:36 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d1a0f811fc8190b6a46a0441159089 |
completed | April 4, 2026, 11:38 p.m. |
Created at: March 30, 2026, 8:22 p.m.