Triple
T2263012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7539 |
E50080
|
entity |
| Predicate | definesBlockSize |
P20328
|
FINISHED |
| Object | 512-bit block for ChaCha20 |
—
|
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: 512-bit block for ChaCha20 | Statement: [RFC 7539, definesBlockSize, 512-bit block for ChaCha20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesBlockSize Context triple: [RFC 7539, definesBlockSize, 512-bit block for ChaCha20]
-
A.
blockSize
chosen
Indicates the size or capacity of a discrete block unit within a larger structure or system.
-
B.
usesAllocationBlockSize
Indicates that one entity operates with or depends on a specific allocation block size defined or provided by another entity.
-
C.
seedSize
Indicates the relative magnitude or dimensions of a seed in comparison to others or to a standard.
-
D.
stateSizeBytes
Indicates the size of a given state or stateful data in terms of the number of bytes it occupies.
-
E.
estimatedNumberOfBlocks
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.