Triple
T32517063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNS-based Authentication of Named Entities |
E831086
|
entity |
| Predicate | certificateUsageModes |
P157756
|
FINISHED |
| Object | CA constraint |
—
|
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: CA constraint | Statement: [DNS-based Authentication of Named Entities, certificateUsageModes, CA constraint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certificateUsageModes Context triple: [DNS-based Authentication of Named Entities, certificateUsageModes, CA constraint]
-
A.
certificateTypesInclude
Indicates that the set of certificate types associated with one entity includes (i.e., contains as members) the certificate types specified by another entity.
-
B.
certificatePurpose
Indicates the intended use or function for which a certificate is issued or valid.
-
C.
keyUsageContext
chosen
Indicates the specific circumstances, purposes, or operational conditions under which a key is intended or permitted to be used.
-
D.
certificatePolicies
Indicates the specific policy rules and usage conditions under which a digital certificate has been issued and is considered valid.
-
E.
certificateType
Indicates the specific kind or category of certificate associated with an entity or relationship.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4aabff08190ad437b687dd41f8d |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.