Triple
T957470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC4 |
E20655
|
entity |
| Predicate | algorithmType |
P21840
|
FINISHED |
| Object | byte-oriented stream cipher |
—
|
LITERAL FINISHED |
How this triple was built (2 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: byte-oriented stream cipher | Statement: [RC4, algorithmType, byte-oriented stream cipher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: algorithmType Context triple: [RC4, algorithmType, byte-oriented stream cipher]
-
A.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
B.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
C.
kernelType
Indicates the specific kind or category of kernel associated with or used by an entity.
-
D.
derivationType
Indicates the specific manner or process by which one entity is derived or obtained from another.
-
E.
checkDigitAlgorithm
Indicates the algorithm or method used to compute or validate a check digit for an identifier or code.
- F. None of above. chosen
Provenance (4 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3fac2bc8190a66feb70c68899b2 |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a18ecc8190883f6206fe3b0fb6 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b326d9d88190913c1a892a795707 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.