Triple
T29443808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSEC3PARAM |
E746789
|
entity |
| Predicate | hashAlgorithmRegistry |
P54503
|
FINISHED |
| Object | IANA DNSSEC NSEC3 Hash Algorithm Registry |
—
|
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: IANA DNSSEC NSEC3 Hash Algorithm Registry | Statement: [NSEC3PARAM, hashAlgorithmRegistry, IANA DNSSEC NSEC3 Hash Algorithm Registry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashAlgorithmRegistry Context triple: [NSEC3PARAM, hashAlgorithmRegistry, IANA DNSSEC NSEC3 Hash Algorithm Registry]
-
A.
hashFamily
Indicates that a hash function belongs to, or is a member of, a particular family of related hash functions.
-
B.
algorithmType
Indicates the specific kind or category of algorithm associated with an entity or process.
-
C.
hasAlgorithmName
chosen
Indicates that an entity is associated with or identified by a specific algorithm name.
-
D.
hashFunction
Indicates a relationship where an input value is transformed into a fixed-size output (hash) according to a specific deterministic hashing algorithm.
-
E.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 3:25 p.m.