Triple
T13636459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1071 |
E325860
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 1141
RFC 1141 is an Internet standard document that revises and replaces earlier guidance on computing the Internet checksum used in IP networking.
|
E1055047
|
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 1141 | Statement: [RFC 1071, obsoletedBy, RFC 1141]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1141 Context triple: [RFC 1071, obsoletedBy, RFC 1141]
-
A.
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.
-
B.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
C.
RFC 1119
RFC 1119 is an early specification in the Network Time Protocol (NTP) series that was later superseded by RFC 1305.
-
D.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
-
E.
RFC 1331
RFC 1331 is an early specification in the Point-to-Point Protocol (PPP) standards series that was later superseded by RFC 1661.
- 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 1141 Triple: [RFC 1071, obsoletedBy, RFC 1141]
Generated description
RFC 1141 is an Internet standard document that revises and replaces earlier guidance on computing the Internet checksum used in IP networking.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1141 Target entity description: RFC 1141 is an Internet standard document that revises and replaces earlier guidance on computing the Internet checksum used in IP networking.
-
A.
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.
-
B.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
C.
RFC 1119
RFC 1119 is an early specification in the Network Time Protocol (NTP) series that was later superseded by RFC 1305.
-
D.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
-
E.
RFC 1331
RFC 1331 is an early specification in the Point-to-Point Protocol (PPP) standards series that was later superseded by RFC 1661.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a616dc81908b8c1213e1d4beed |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f794307c288190a0f4629bf5e2b0d9 |
completed | May 3, 2026, 6:30 p.m. |
| NEDg | Description generation | batch_69f79655d5f08190a3cbf3e12e2ffa67 |
completed | May 3, 2026, 6:39 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f7972a1cf48190a1d435227414967a |
completed | May 3, 2026, 6:42 p.m. |
Created at: April 9, 2026, 9:51 p.m.