Triple
T9403318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AES-Poly1305 |
E226526
|
entity |
| Predicate | nonceType |
P27631
|
FINISHED |
| Object | unique per key |
—
|
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: unique per key | Statement: [AES-Poly1305, nonceType, unique per key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonceType Context triple: [AES-Poly1305, nonceType, unique per key]
-
A.
usesNonce
chosen
Indicates that one entity employs a nonce (a unique, typically one-time-use value) as part of its interaction or operation with another entity.
-
B.
nativeToken
Indicates that the referenced token is the primary, built-in cryptocurrency or asset of a given blockchain or platform, as opposed to a secondary or issued token.
-
C.
credentialType
Indicates the specific kind or category of credential associated with an entity or relationship.
-
D.
notationType
Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
-
E.
tokenType
Indicates the classification or category assigned to a token within a sequence, such as its syntactic, semantic, or functional role.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51bf7e5c8190850b671778496150 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.