Triple
T7414668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCMP |
E171099
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object |
RFC 3610
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
|
E663888
|
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 3610 | Statement: [CCMP, definedIn, RFC 3610]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3610 Context triple: [CCMP, definedIn, RFC 3610]
-
A.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
B.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
C.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
D.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
E.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
- 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 3610 Triple: [CCMP, definedIn, RFC 3610]
Generated description
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3610 Target entity description: RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
-
A.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
B.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
C.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
D.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
E.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c509ac8190876f207267a33a3b |
completed | March 27, 2026, 9:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c81ee1b48c81909912ff0d7bf2837e |
completed | March 28, 2026, 6:33 p.m. |
| NEDg | Description generation | batch_69c81fb91eb88190b6436ace69d44211 |
completed | March 28, 2026, 6:36 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c822f547388190be0879b70542a421 |
completed | March 28, 2026, 6:50 p.m. |
Created at: March 27, 2026, 3:11 p.m.