Triple
T10243963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5751 |
E197861
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2633
RFC 2633 is an earlier Internet standards document that specified the original S/MIME Version 3 message specification for secure email before being superseded by RFC 5751.
|
E853539
|
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 2633 | Statement: [RFC 5751, obsoletes, RFC 2633]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2633 Context triple: [RFC 5751, obsoletes, RFC 2633]
-
A.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
B.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
C.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1533
RFC 1533 is an early Internet standards document that originally specified DHCP and BOOTP vendor extensions and options before being superseded by later updates.
-
E.
RFC 2433
RFC 2433 is an older Internet Engineering Task Force (IETF) specification that was later superseded by RFC 4250 as part of updates to SSH-related protocol definitions.
- 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 2633 Triple: [RFC 5751, obsoletes, RFC 2633]
Generated description
RFC 2633 is an earlier Internet standards document that specified the original S/MIME Version 3 message specification for secure email before being superseded by RFC 5751.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2633 Target entity description: RFC 2633 is an earlier Internet standards document that specified the original S/MIME Version 3 message specification for secure email before being superseded by RFC 5751.
-
A.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
B.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
C.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1533
RFC 1533 is an early Internet standards document that originally specified DHCP and BOOTP vendor extensions and options before being superseded by later updates.
-
E.
RFC 2433
RFC 2433 is an older Internet Engineering Task Force (IETF) specification that was later superseded by RFC 4250 as part of updates to SSH-related protocol definitions.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d22a76188190a73df23bfb08eb3d |
completed | April 7, 2026, 9:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f7936ce4819087f07df2c7a76282 |
completed | April 9, 2026, 12:49 a.m. |
| NEDg | Description generation | batch_69d6fa2f7a848190a9de5de4d0f3f110 |
completed | April 9, 2026, 1 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d6fcbab3ec8190ade1c0223c22ad58 |
completed | April 9, 2026, 1:11 a.m. |
Created at: April 6, 2026, 11:26 a.m.