Triple
T25931738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux kernel crypto API |
E653453
|
entity |
| Predicate | supportsAlgorithmClass |
P32439
|
FINISHED |
| Object | symmetric ciphers |
—
|
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: symmetric ciphers | Statement: [Linux kernel crypto API, supportsAlgorithmClass, symmetric ciphers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAlgorithmClass Context triple: [Linux kernel crypto API, supportsAlgorithmClass, symmetric ciphers]
-
A.
supportedClass
chosen
Indicates that one entity is a class or type that is recognized, handled, or operable within the capabilities or context provided by another entity.
-
B.
hasComponentAlgorithm
Indicates that an entity includes or is composed of a specific algorithm as one of its constituent components.
-
C.
hasAlgorithmName
Indicates that an entity is associated with or identified by a specific algorithm name.
-
D.
supportsOptimizationAlgorithm
Indicates that one entity is capable of running, integrating, or being compatible with a specified optimization algorithm.
-
E.
usesSignatureAlgorithm
Indicates that one entity employs a specific signature algorithm to create or verify digital signatures for another entity or data.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 22, 2026, 8:37 a.m.