Triple
T29142139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5702 |
E738665
|
entity |
| Predicate | definesAlgorithmForDNSSEC |
P145700
|
FINISHED |
| Object | RSA/SHA-256 |
—
|
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: RSA/SHA-256 | Statement: [RFC 5702, definesAlgorithmForDNSSEC, RSA/SHA-256]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesAlgorithmForDNSSEC Context triple: [RFC 5702, definesAlgorithmForDNSSEC, RSA/SHA-256]
-
A.
rootZoneSigned
Indicates that the DNS root zone has been cryptographically signed, typically using DNSSEC, to provide data integrity and authentication.
-
B.
DNSSECSupported
Indicates that a domain or DNS service supports and correctly implements DNSSEC security extensions for authenticating DNS data.
-
C.
usesSignatureAlgorithm
Indicates that one entity employs a specific signature algorithm to create or verify digital signatures for another entity or data.
-
D.
associatedWithAlgorithm
chosen
Indicates that one entity has a connection or linkage to a specific algorithm, such as using, implementing, or being defined in terms of that algorithm.
-
E.
algorithmType
Indicates the specific kind or category of algorithm associated with an entity or process.
- 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_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 28, 2026, 11:37 a.m.