Triple
T25425264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDSEED |
E637100
|
entity |
| Predicate | entropySource |
P110259
|
FINISHED |
| Object | on-chip hardware entropy source |
—
|
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 hardware entropy source | Statement: [RDSEED, entropySource, on-chip hardware entropy source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entropySource Context triple: [RDSEED, entropySource, on-chip hardware entropy source]
-
A.
saltSource
Indicates that one entity serves as the origin or provider of salt for another entity or process.
-
B.
hasEntropy
Indicates that an entity possesses or is characterized by a certain amount or state of entropy, typically reflecting its degree of disorder or uncertainty.
-
C.
MagicSeed
Indicates a relationship where an entity functions as or originates from a seed possessing magical or supernatural properties that can cause extraordinary effects or growth.
-
D.
originSecret
Indicates that the true source or origin of an entity is hidden, confidential, or not publicly disclosed.
-
E.
samplingSource
chosen
Indicates that one entity serves as the origin or provider from which another entity is sampled or drawn.
- 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_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:57 p.m.