Triple

T32517046
Position Surface form Disambiguated ID Type / Status
Subject DNS-based Authentication of Named Entities E831086 entity
Predicate definedIn P775 FINISHED
Object RFC 7673
RFC 7673 is an Internet standard that specifies the DNS-based Authentication of Named Entities (DANE) protocol for using DNSSEC to associate domain names with cryptographic certificates and improve secure communications.
E2011643 NE 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: RFC 7673 | Statement: [DNS-based Authentication of Named Entities, definedIn, RFC 7673]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 7673
Triple: [DNS-based Authentication of Named Entities, definedIn, RFC 7673]
Generated description
RFC 7673 is an Internet standard that specifies the DNS-based Authentication of Named Entities (DANE) protocol for using DNSSEC to associate domain names with cryptographic certificates and improve secure communications.

Provenance (5 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.
NED1 Entity disambiguation (via context triple) batch_6a347b7cf564819089e9f116f5fe635f completed June 18, 2026, 11:13 p.m.
NEDg Description generation batch_6a347c8c8d1881909646d6cdf1230f78 completed June 18, 2026, 11:17 p.m.
NED2 Entity disambiguation (via description) batch_6a347d6a097881909f078a5dbbdf4e1f completed June 18, 2026, 11:21 p.m.
Created at: May 1, 2026, 1 a.m.