Triple
T9818127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1655 |
E238459
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 2358
RFC 2358 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to the Point-to-Point Protocol (PPP) and its associated network control protocols.
|
E823481
|
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 2358 | Statement: [RFC 1655, obsoletedBy, RFC 2358]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2358 Context triple: [RFC 1655, obsoletedBy, RFC 2358]
-
A.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 858
RFC 858 is an early Internet standard that defines the Telnet protocol’s status option, specifying how a Telnet client and server can exchange information about their current status.
-
D.
RFC 2865
RFC 2865 is the IETF standard that specifies the Remote Authentication Dial-In User Service (RADIUS) protocol for centralized authentication, authorization, and accounting in network access.
-
E.
RFC 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
- 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 2358 Triple: [RFC 1655, obsoletedBy, RFC 2358]
Generated description
RFC 2358 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to the Point-to-Point Protocol (PPP) and its associated network control protocols.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2358 Target entity description: RFC 2358 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to the Point-to-Point Protocol (PPP) and its associated network control protocols.
-
A.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 858
RFC 858 is an early Internet standard that defines the Telnet protocol’s status option, specifying how a Telnet client and server can exchange information about their current status.
-
D.
RFC 2865
RFC 2865 is the IETF standard that specifies the Remote Authentication Dial-In User Service (RADIUS) protocol for centralized authentication, authorization, and accounting in network access.
-
E.
RFC 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f5bfa481908a2d2cb3f3d7d585 |
completed | April 2, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc70d1188190820a49766699b94a |
completed | April 5, 2026, 2:44 a.m. |
| NEDg | Description generation | batch_69d1cf9669308190a58e58b86e652801 |
completed | April 5, 2026, 2:57 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d1d0034dc081908182e3f873a2c584 |
completed | April 5, 2026, 2:59 a.m. |
Created at: March 30, 2026, 8:31 p.m.