Triple
T10926987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6066 |
E258094
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 4366
RFC 4366 is an earlier IETF specification that extended TLS with additional client and server features, later superseded and refined by RFC 6066.
|
E893547
|
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 4366 | Statement: [RFC 6066, obsoletes, RFC 4366]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4366 Context triple: [RFC 6066, obsoletes, RFC 4366]
-
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 3996
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
-
C.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
D.
RFC 4516
RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
-
E.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
- 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 4366 Triple: [RFC 6066, obsoletes, RFC 4366]
Generated description
RFC 4366 is an earlier IETF specification that extended TLS with additional client and server features, later superseded and refined by RFC 6066.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 4366 Target entity description: RFC 4366 is an earlier IETF specification that extended TLS with additional client and server features, later superseded and refined by RFC 6066.
-
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 3996
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
-
C.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
D.
RFC 4516
RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
-
E.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709165188190aa30dd08deddade4 |
completed | April 9, 2026, 9:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e217475344819088b44b6efb2df1c8 |
completed | April 17, 2026, 11:19 a.m. |
| NEDg | Description generation | batch_69e21d8aea2881908ac8f5225b8739c5 |
completed | April 17, 2026, 11:46 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69e21eb18a1881908ded331db89063ed |
completed | April 17, 2026, 11:51 a.m. |
Created at: April 8, 2026, 9:22 p.m.