Triple
T18359822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabin–Karp algorithm |
E439883
|
entity |
| Predicate | hashFunctionType |
P8884
|
FINISHED |
| Object | polynomial rolling hash |
—
|
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: polynomial rolling hash | Statement: [Rabin–Karp algorithm, hashFunctionType, polynomial rolling hash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashFunctionType Context triple: [Rabin–Karp algorithm, hashFunctionType, polynomial rolling hash]
-
A.
hashFunction
chosen
Indicates a relationship where an input value is transformed into a fixed-size output (hash) according to a specific deterministic hashing algorithm.
-
B.
roundFunctionType
Indicates that a function or operation is of a type that performs a rounding transformation on its input values.
-
C.
algorithmType
Indicates the specific kind or category of algorithm associated with an entity or process.
-
D.
cryptFunction
Indicates a function or method that performs cryptographic processing, such as encrypting, decrypting, or otherwise transforming data using a cryptographic algorithm.
-
E.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516d9dba8819088c5d772e3ee670d |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.