Triple
T29142192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNSKEY |
E738666
|
entity |
| Predicate | isAuthenticatedBy |
P94618
|
FINISHED |
| Object | DS record in parent zone |
—
|
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: DS record in parent zone | Statement: [DNSKEY, isAuthenticatedBy, DS record in parent zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAuthenticatedBy Context triple: [DNSKEY, isAuthenticatedBy, DS record in parent zone]
-
A.
isAuthorityFor
Indicates that one entity holds recognized power, control, or decision-making responsibility over another entity or domain.
-
B.
authorizedIn
Indicates that an entity has been granted official permission or legal authority to act, operate, or be valid within a specified context, domain, or jurisdiction.
-
C.
overseesAuthenticationOf
chosen
Indicates that one entity is responsible for supervising, managing, or ensuring the proper execution of another entity’s authentication process.
-
D.
isAuthentic
Indicates that something is genuine, real, or true to its claimed origin, nature, or standard.
-
E.
authorizedAs
Indicates that one entity is granted permission to act in the role, capacity, or identity of another entity.
- 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_69f6626fc3088190970ae48003cf2bf5 |
completed | May 2, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:37 a.m.