Triple
T25931711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AESENCLAST |
E653452
|
entity |
| Predicate | usesExecutionUnit |
P43652
|
FINISHED |
| Object | AES-NI hardware unit |
—
|
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: AES-NI hardware unit | Statement: [AESENCLAST, usesExecutionUnit, AES-NI hardware unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesExecutionUnit Context triple: [AESENCLAST, usesExecutionUnit, AES-NI hardware unit]
-
A.
executionUnits
Indicates a relationship where a process, task, or operation is carried out by one or more specific execution units (such as cores, threads, or processing elements).
-
B.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
C.
isExecutedFor
Indicates that an action, plan, or process is carried out on behalf of, or in service of, a particular entity or purpose.
-
D.
usesCoherentUnit
Indicates that one entity employs a consistent, logically compatible system of units in relation to another entity or context.
-
E.
executionDevice
chosen
Indicates that an entity serves as the instrument, tool, or device used to carry out or execute a particular action or process.
- 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_69f604192b6c8190b86e151a628eafd8 |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:37 a.m.