Triple
T29142193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNSKEY |
E738666
|
entity |
| Predicate | isUsedToVerify |
P23056
|
FINISHED |
| Object | RRSIG 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 records | Statement: [DNSKEY, isUsedToVerify, RRSIG records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedToVerify Context triple: [DNSKEY, isUsedToVerify, RRSIG records]
-
A.
usedToAuthorize
Indicates that something serves as the basis or instrument for granting permission, approval, or official power to perform an action.
-
B.
isBelievedToBeUsedFor
Indicates that something is thought or assumed to serve a particular purpose or function, without certainty.
-
C.
isUsedToTest
chosen
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
-
D.
isIntendedForUseBy
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
-
E.
verificationBasis
Indicates the underlying evidence, method, or criteria used to confirm or validate that something is true, correct, or compliant.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 11:37 a.m.