Triple
T11327224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XChaCha20-Poly1305 AEAD construction |
E268251
|
entity |
| Predicate | hasKeyLength |
P8686
|
FINISHED |
| Object | 256 bits |
—
|
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: 256 bits | Statement: [XChaCha20-Poly1305 AEAD construction, hasKeyLength, 256 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyLength Context triple: [XChaCha20-Poly1305 AEAD construction, hasKeyLength, 256 bits]
-
A.
supportsKeyLength
chosen
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
-
B.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
-
C.
hasFieldLength
Indicates that an entity possesses a field whose length (such as number of characters or size) is specified or constrained.
-
D.
hasKeyStructure
Indicates that one entity possesses or defines the primary structural framework or core structural pattern of another entity.
-
E.
hasKeyQuantity
Indicates that an entity is associated with a primary or defining quantity that characterizes or measures it.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e2253881909518cad0f12ef612 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.