Triple
T33057296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grain v1 |
E845875
|
entity |
| Predicate | hasKeyStreamGenerationMethod |
P75139
|
FINISHED |
| Object | LFSR and NFSR based keystream generation |
—
|
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: LFSR and NFSR based keystream generation | Statement: [Grain v1, hasKeyStreamGenerationMethod, LFSR and NFSR based keystream generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyStreamGenerationMethod Context triple: [Grain v1, hasKeyStreamGenerationMethod, LFSR and NFSR based keystream generation]
-
A.
hasGenerationCode
Indicates that an entity is associated with a specific generation code that identifies its generational category or version.
-
B.
hasGeneratingFunction
Indicates that one entity serves as the generating function associated with, or defining, another entity.
-
C.
hasGeneratorType
chosen
Indicates that an entity is associated with or uses a specific type or category of generator.
-
D.
hasGenerationRelationship
Indicates that one entity is involved in producing, creating, or giving rise to another entity.
-
E.
hasReleaseGeneration
Indicates that one entity is associated with a particular release generation or version cycle of another entity.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:25 a.m.