Triple
T25425209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Secure Key |
E637099
|
entity |
| Predicate | entropySourceType |
P38247
|
FINISHED |
| Object | on-chip digital circuitry |
—
|
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: on-chip digital circuitry | Statement: [Intel Secure Key, entropySourceType, on-chip digital circuitry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entropySourceType Context triple: [Intel Secure Key, entropySourceType, on-chip digital circuitry]
-
A.
saltSource
Indicates that one entity serves as the origin or provider of salt for another entity or process.
-
B.
usesSourceType
chosen
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
C.
mainSourceType
Indicates the primary category or kind of source from which something originates or is derived.
-
D.
originSecret
Indicates that the true source or origin of an entity is hidden, confidential, or not publicly disclosed.
-
E.
vulnerabilitySource
Indicates that one entity is the origin, cause, or contributing factor of another entity’s vulnerability or weakness.
- 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_69f5f6bf25c881909f049d5393927bfb |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:57 p.m.