Triple
T11327226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XChaCha20-Poly1305 AEAD construction |
E268251
|
entity |
| Predicate | hasTagLength |
P98521
|
FINISHED |
| Object | 128 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: 128 bits | Statement: [XChaCha20-Poly1305 AEAD construction, hasTagLength, 128 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTagLength Context triple: [XChaCha20-Poly1305 AEAD construction, hasTagLength, 128 bits]
-
A.
supportsTagLength
Indicates that an entity is capable of handling or enforcing a specified tag length.
-
B.
hasFieldLength
Indicates that an entity possesses a field whose length (such as number of characters or size) is specified or constrained.
-
C.
hasSectionLength
Indicates that an entity is associated with a specific length value for one of its sections.
-
D.
hasLineLength
Indicates that one entity has, is characterized by, or is associated with a specific line length value.
-
E.
hasLengthRange
Indicates that an entity’s length falls within a specified minimum-to-maximum range.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.