Triple
T29142135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5702 |
E738665
|
entity |
| Predicate | hashAlgorithmFamily |
P160519
|
FINISHED |
| Object | SHA-2 |
—
|
NE NERFINISHED |
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: SHA-2 | Statement: [RFC 5702, hashAlgorithmFamily, SHA-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashAlgorithmFamily Context triple: [RFC 5702, hashAlgorithmFamily, SHA-2]
-
A.
hashFamily
chosen
Indicates that a hash function belongs to, or is a member of, a particular family of related hash functions.
-
B.
algorithmFamily
Indicates that one algorithm belongs to, or is categorized under, a broader family or class of related algorithms.
-
C.
algorithmType
Indicates the specific kind or category of algorithm associated with an entity or process.
-
D.
blockCipherFamily
Indicates that one entity is a family or category of related block cipher algorithms to which the other entity belongs.
-
E.
cryptographicType
Indicates the specific kind or category of cryptographic method, algorithm, or primitive associated with an entity or operation.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 11:37 a.m.