Triple
T26408663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keccak |
E663897
|
entity |
| Predicate | influencedStandard |
P9
|
FINISHED |
| Object | SHAKE128 |
—
|
NE NERFINISHED |
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: SHAKE128 | Statement: [Keccak, influencedStandard, SHAKE128]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedStandard Context triple: [Keccak, influencedStandard, SHAKE128]
-
A.
standardizationInfluence
Indicates the extent to which one entity’s standards, norms, or standardization efforts shape, guide, or constrain another entity’s practices, processes, or specifications.
-
B.
influenced
chosen
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
-
C.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
-
D.
influencedAspectOf
Indicates that one entity has affected, shaped, or altered a particular aspect or component of another entity.
-
E.
incorporatesInfluence
Indicates that one entity integrates or absorbs the influence, ideas, or characteristics of another into itself.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 26, 2026, 11:36 p.m.