Triple
T37123867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HChaCha20 |
E919336
|
entity |
| Predicate | outputSelection |
P16786
|
FINISHED |
| Object | first 4 state words and last 4 state words |
—
|
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: first 4 state words and last 4 state words | Statement: [HChaCha20, outputSelection, first 4 state words and last 4 state words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputSelection Context triple: [HChaCha20, outputSelection, first 4 state words and last 4 state words]
-
A.
selectionFrom
chosen
Indicates that one entity is chosen as a member or subset from a larger set or collection represented by another entity.
-
B.
encodingSelection
Indicates that an entity chooses or specifies a particular encoding method or format to be used in a given context.
-
C.
outputIs
Indicates that one entity functions as the result, product, or outcome produced by another entity or process.
-
D.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another entity.
-
E.
outputOf
Indicates that one entity is the result or product generated by the processing, operation, or behavior 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.