Triple
T32582084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hash-based Message Authentication Code |
E832816
|
entity |
| Predicate | tagLengthLimitedBy |
P174618
|
FINISHED |
| Object | output size of underlying hash function |
—
|
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: output size of underlying hash function | Statement: [Hash-based Message Authentication Code, tagLengthLimitedBy, output size of underlying hash function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tagLengthLimitedBy Context triple: [Hash-based Message Authentication Code, tagLengthLimitedBy, output size of underlying hash function]
-
A.
supportsTagLength
Indicates that an entity is capable of handling or enforcing a specified tag length.
-
B.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
-
C.
hasCategoryLengthRestriction
Indicates that there is a constraint on the allowable length of a category, such as its name, identifier, or structural size.
-
D.
usableLength
Indicates the portion of an object’s total length that can actually be used for its intended function or purpose.
-
E.
identifierLength
Indicates the length or number of characters in an entity’s identifier.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c669d6408190bc26dbf21f59e237 |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c2df27ec8190912ec8eb488836d0 |
completed | May 3, 2026, 3:37 a.m. |
Created at: May 1, 2026, 1:04 a.m.