Triple
T26916323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigenère table |
E677525
|
entity |
| Predicate | cipherTypeSupported |
P135207
|
FINISHED |
| Object | polyalphabetic substitution 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: polyalphabetic substitution cipher | Statement: [Vigenère table, cipherTypeSupported, polyalphabetic substitution cipher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cipherTypeSupported Context triple: [Vigenère table, cipherTypeSupported, polyalphabetic substitution cipher]
-
A.
encryptionModeSupport
Indicates that an entity supports or is compatible with a specified mode of encryption.
-
B.
supportsCipherSuite
Indicates that one entity is capable of using or handling a specified cryptographic cipher suite in secure communications.
-
C.
cryptographicType
chosen
Indicates the specific kind or category of cryptographic method, algorithm, or primitive associated with an entity or operation.
-
D.
ciphertextType
Indicates the specific kind or format of ciphertext produced or used in an encryption process.
-
E.
canBeEncryptedUsing
Indicates that one entity is capable of being transformed into a secure, encoded form by applying the encryption method or key represented by another entity.
- F. None of above.
Provenance (3 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fde093c81908c03c224547b251f |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:04 a.m.