Triple
T37123862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HChaCha20 |
E919336
|
entity |
| Predicate | constantWords |
P32464
|
FINISHED |
| Object | "expand 32-byte k" constants |
—
|
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: "expand 32-byte k" constants | Statement: [HChaCha20, constantWords, "expand 32-byte k" constants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constantWords Context triple: [HChaCha20, constantWords, "expand 32-byte k" constants]
-
A.
constant
Indicates that the relationship or value does not change across different instances, contexts, or over time.
-
B.
constantType
Indicates that one entity is a constant whose value or nature is of the specified type.
-
C.
constantName
Indicates that an entity has a specific, fixed identifier or label used as a constant within a system or context.
-
D.
constantRepresents
Indicates that one entity is a constant that symbolically stands for or denotes another entity or value.
-
E.
firstWordsOf
chosen
Indicates that one entity consists of the initial word or sequence of words taken from another entity (such as a text or utterance).
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:15 p.m.