Triple
T25425457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLMUL |
E637104
|
entity |
| Predicate | usedByLibrary |
P57368
|
FINISHED |
| Object | Linux kernel crypto API |
—
|
NE NERFINISHED |
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: Linux kernel crypto API | Statement: [CLMUL, usedByLibrary, Linux kernel crypto API]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByLibrary Context triple: [CLMUL, usedByLibrary, Linux kernel crypto API]
-
A.
usedInLibrary
chosen
Indicates that something is utilized or applied within the context of a library, such as a software library or a physical library system.
-
B.
libraryUsed
Indicates that one entity makes use of another entity as a software or code library to provide functionality or services.
-
C.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
D.
implementedInLibrary
Indicates that a particular functionality, feature, or component is realized and provided within a specific software library.
-
E.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 1:57 p.m.