Triple
T9768826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4513 |
E237066
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2830
RFC 2830 is an Internet standard that originally specified how to use Transport Layer Security (TLS) to secure LDAP (Lightweight Directory Access Protocol) connections.
|
E821315
|
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 2830 | Statement: [RFC 4513, obsoletes, RFC 2830]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2830 Context triple: [RFC 4513, obsoletes, RFC 2830]
-
A.
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.
-
B.
RFC 2030
RFC 2030 is an Internet Engineering Task Force (IETF) specification that defined the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
-
C.
RFC 3380
RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
-
D.
RFC 3008
RFC 3008 is an earlier Internet Engineering Task Force (IETF) standards document related to DNS security that was later superseded by RFC 4033.
-
E.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
- 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 2830 Triple: [RFC 4513, obsoletes, RFC 2830]
Generated description
RFC 2830 is an Internet standard that originally specified how to use Transport Layer Security (TLS) to secure LDAP (Lightweight Directory Access Protocol) connections.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2830 Target entity description: RFC 2830 is an Internet standard that originally specified how to use Transport Layer Security (TLS) to secure LDAP (Lightweight Directory Access Protocol) connections.
-
A.
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.
-
B.
RFC 2030
RFC 2030 is an Internet Engineering Task Force (IETF) specification that defined the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
-
C.
RFC 3380
RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
-
D.
RFC 3008
RFC 3008 is an earlier Internet Engineering Task Force (IETF) standards document related to DNS security that was later superseded by RFC 4033.
-
E.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f0c64c81908f3435dd49c0218b |
completed | April 1, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c4154af081908ca743b43ade83c7 |
completed | April 5, 2026, 2:08 a.m. |
| NEDg | Description generation | batch_69d1c4d62a78819089ece2bb1f5fb66b |
completed | April 5, 2026, 2:11 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d1c589b90481908bc0944868d648b2 |
completed | April 5, 2026, 2:14 a.m. |
Created at: March 30, 2026, 8:25 p.m.