Triple
T5214013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blum–Micali pseudorandom number generator |
E117703
|
entity |
| Predicate | seedSpace |
P62074
|
FINISHED |
| Object | elements of the underlying group |
—
|
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: elements of the underlying group | Statement: [Blum–Micali pseudorandom number generator, seedSpace, elements of the underlying group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seedSpace Context triple: [Blum–Micali pseudorandom number generator, seedSpace, elements of the underlying group]
-
A.
seedUse
Indicates the use or application of seeds for a particular purpose, such as planting, cultivation, or propagation.
-
B.
seedType
Indicates the specific kind or category of seed associated with an entity.
-
C.
seedSize
Indicates the relative magnitude or dimensions of a seed in comparison to others or to a standard.
-
D.
seedProduct
Indicates that one entity serves as the original or source product from which another related product is derived or initialized.
-
E.
spaceDomain
Indicates that the relationship or activity occurs within, pertains to, or is governed by the space domain (outer space and related space operations).
- F. None of above. chosen
Provenance (4 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a911d40819086621537274dc0f0 |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79000cf88190b3c05d95395b0cd2 |
completed | March 20, 2026, 4:42 p.m. |
Created at: March 20, 2026, 1:47 p.m.