Triple
T8009161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4033 |
E186439
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 3445
RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
|
E707273
|
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 3445 | Statement: [RFC 4033, obsoletes, RFC 3445]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3445 Context triple: [RFC 4033, obsoletes, RFC 3445]
-
A.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
B.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
C.
RFC 4555
RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
-
D.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
E.
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
- 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 3445 Triple: [RFC 4033, obsoletes, RFC 3445]
Generated description
RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3445 Target entity description: RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
-
A.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
B.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
C.
RFC 4555
RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
-
D.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
E.
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d6f76408190a1312369521a187a |
completed | March 31, 2026, 3:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc569e90d48190a1bf1495496017f8 |
completed | March 31, 2026, 11:19 p.m. |
| NEDg | Description generation | batch_69cc58a8f3d08190bec84dc1ba3b5b84 |
completed | March 31, 2026, 11:28 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cc5cb791b48190bd5004b518d23f84 |
completed | March 31, 2026, 11:45 p.m. |
Created at: March 30, 2026, 5:19 p.m.