Triple
T7414987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galois/Counter Mode |
E171106
|
entity |
| Predicate | encryptionStructure |
P30780
|
FINISHED |
| Object | counter mode |
—
|
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: counter mode | Statement: [Galois/Counter Mode, encryptionStructure, counter mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encryptionStructure Context triple: [Galois/Counter Mode, encryptionStructure, counter mode]
-
A.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
B.
encryptionDirection
Indicates the direction in which data is being encrypted, specifying whether it is going from source to destination or vice versa.
-
C.
storageStructure
Indicates a relationship where one entity serves as a physical or logical structure used to store or contain another entity.
-
D.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
E.
cryptographicModel
chosen
Indicates a relationship where one entity serves as, or is based on, a particular cryptographic scheme, framework, or formal model.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c643248190a387abba2f482b25 |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.