Triple

T25932144
Position Surface form Disambiguated ID Type / Status
Subject AMD SEV E653461 entity
Predicate implementedBy P172 FINISHED
Object AMD Secure Processor
The AMD Secure Processor is a dedicated security subsystem integrated into AMD CPUs that provides hardware-based cryptographic and isolation capabilities to protect sensitive data and enable features like secure encrypted virtualization.
E1701712 NE 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: AMD Secure Processor | Statement: [AMD SEV, implementedBy, AMD Secure Processor]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: AMD Secure Processor
Triple: [AMD SEV, implementedBy, AMD Secure Processor]
Generated description
The AMD Secure Processor is a dedicated security subsystem integrated into AMD CPUs that provides hardware-based cryptographic and isolation capabilities to protect sensitive data and enable features like secure encrypted virtualization.

Provenance (5 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.
NED1 Entity disambiguation (via context triple) batch_6a10ecdad4f08190b6c583e9278198de completed May 22, 2026, 11:55 p.m.
NEDg Description generation batch_6a10f0f8baa48190baadfadfb4e74918 completed May 23, 2026, 12:12 a.m.
NED2 Entity disambiguation (via description) batch_6a10f163401c8190a442477305cfed1d completed May 23, 2026, 12:14 a.m.
Created at: April 22, 2026, 8:37 a.m.