Triple
T7934678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAST5 |
E184258
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object |
RFC 2144
RFC 2144 is an Internet standards document that specifies the CAST-128 (CAST5) symmetric-key block cipher for use in cryptographic applications.
|
E705940
|
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 2144 | Statement: [CAST5, standardizedIn, RFC 2144]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2144 Context triple: [CAST5, standardizedIn, RFC 2144]
-
A.
RFC 1443
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
-
B.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
C.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
-
D.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
E.
RFC 1654
RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
- 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 2144 Triple: [CAST5, standardizedIn, RFC 2144]
Generated description
RFC 2144 is an Internet standards document that specifies the CAST-128 (CAST5) symmetric-key block cipher for use in cryptographic applications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2144 Target entity description: RFC 2144 is an Internet standards document that specifies the CAST-128 (CAST5) symmetric-key block cipher for use in cryptographic applications.
-
A.
RFC 1443
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
-
B.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
C.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
-
D.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
E.
RFC 1654
RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aeb132c8190bea4906aaf51b869 |
completed | March 31, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc564a4fac8190972f9dfa7c026ea8 |
completed | March 31, 2026, 11:18 p.m. |
| NEDg | Description generation | batch_69cc5822581481908a143376bee599ec |
completed | March 31, 2026, 11:26 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cc58f549388190ba6c8b41c0820cd6 |
completed | March 31, 2026, 11:29 p.m. |
Created at: March 30, 2026, 5:08 p.m.