Triple
T9690787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5905 |
E234528
|
entity |
| Predicate | isObsoletedBy |
P101
|
FINISHED |
| Object |
RFC 9589
RFC 9589 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the Network Time Protocol version 4 (NTPv4) specification to address modern requirements and improvements in time synchronization.
|
E815700
|
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 9589 | Statement: [RFC 5905, isObsoletedBy, RFC 9589]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 9589 Context triple: [RFC 5905, isObsoletedBy, RFC 9589]
-
A.
RFC 9293
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
-
B.
RFC 9082
RFC 9082 is an IETF standard that specifies the HTTP-based query format and response structure for the Registration Data Access Protocol (RDAP), used to access domain name and Internet number registration data.
-
C.
RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
D.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
E.
RFC 7158
RFC 7158 is an IETF specification that updates and clarifies the JSON (JavaScript Object Notation) data interchange format previously defined in RFC 4627.
- 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 9589 Triple: [RFC 5905, isObsoletedBy, RFC 9589]
Generated description
RFC 9589 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the Network Time Protocol version 4 (NTPv4) specification to address modern requirements and improvements in time synchronization.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 9589 Target entity description: RFC 9589 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the Network Time Protocol version 4 (NTPv4) specification to address modern requirements and improvements in time synchronization.
-
A.
RFC 9293
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
-
B.
RFC 9082
RFC 9082 is an IETF standard that specifies the HTTP-based query format and response structure for the Registration Data Access Protocol (RDAP), used to access domain name and Internet number registration data.
-
C.
RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
D.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
E.
RFC 7158
RFC 7158 is an IETF specification that updates and clarifies the JSON (JavaScript Object Notation) data interchange format previously defined in RFC 4627.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d0422e88190a234ba74eb0dad25 |
completed | April 1, 2026, 10:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19118874c81909a97f874b1dc2db8 |
completed | April 4, 2026, 10:30 p.m. |
| NEDg | Description generation | batch_69d193a5cdac8190b84564f397d00124 |
completed | April 4, 2026, 10:41 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d19457c6488190a7bc72e1a27c088a |
completed | April 4, 2026, 10:44 p.m. |
Created at: March 30, 2026, 8:17 p.m.