Triple
T5770879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5340 |
E127327
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
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.
|
E549517
|
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 5838 | Statement: [RFC 5340, obsoletedBy, RFC 5838]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5838 Context triple: [RFC 5340, obsoletedBy, RFC 5838]
-
A.
RFC 5338
RFC 5338 is an Internet Engineering Task Force (IETF) document that specified an earlier approach to managing the IANA IPv6 Special-Purpose Address Registry before being superseded by a later standard.
-
B.
RFC 5508
RFC 5508 is an Internet Engineering Task Force (IETF) standards document that specifies requirements and mechanisms related to IP networking, later refined and updated by RFC 6146.
-
C.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
D.
RFC 5382
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- 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 5838 Triple: [RFC 5340, obsoletedBy, RFC 5838]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 5838 Target entity description: 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.
-
A.
RFC 5338
RFC 5338 is an Internet Engineering Task Force (IETF) document that specified an earlier approach to managing the IANA IPv6 Special-Purpose Address Registry before being superseded by a later standard.
-
B.
RFC 5508
RFC 5508 is an Internet Engineering Task Force (IETF) standards document that specifies requirements and mechanisms related to IP networking, later refined and updated by RFC 6146.
-
C.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
D.
RFC 5382
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029ac21ec81908d88ba72e966d7cb |
completed | March 22, 2026, 5:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a16ea7108190adb0756dac94c42c |
completed | March 23, 2026, 2:11 a.m. |
| NEDg | Description generation | batch_69c0a27765688190b02a1b0cd39a87fe |
completed | March 23, 2026, 2:16 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c0a2fd7ec081909033994e5556a6ae |
completed | March 23, 2026, 2:18 a.m. |
Created at: March 22, 2026, 3:50 p.m.