Triple
T7414819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rijndael |
E171102
|
entity |
| Predicate | usesSBox |
P76797
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rijndael, usesSBox, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSBox Context triple: [Rijndael, usesSBox, yes]
-
A.
usesScrambling
Indicates that one entity applies a scrambling process or technique to another entity or to information associated with it.
-
B.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
C.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c509ac8190876f207267a33a3b |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1c3307481909a7f6bb69d4fddac |
completed | March 27, 2026, 9:08 p.m. |
Created at: March 27, 2026, 3:11 p.m.