Triple
T1907789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNSSEC ZSK |
E38040
|
entity |
| Predicate | verificationInput |
P4965
|
FINISHED |
| Object | RRSIG and DNSKEY records |
—
|
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: RRSIG and DNSKEY records | Statement: [DNSSEC ZSK, verificationInput, RRSIG and DNSKEY records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verificationInput Context triple: [DNSSEC ZSK, verificationInput, RRSIG and DNSKEY records]
-
A.
confirmationMethod
chosen
Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
-
B.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
C.
dataTypeVerified
Indicates that the data’s type has been checked and confirmed to match the expected or required type.
-
D.
inscriptionCompleteness
Indicates how fully or partially an inscription is preserved or recorded in relation to its original state.
-
E.
visualForm
Indicates the visual appearance, shape, or structural pattern that characterizes how something looks.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.