Triple
T32517395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .name |
E831093
|
entity |
| Predicate | dnsProtocol |
P31215
|
FINISHED |
| Object | DNS |
—
|
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: DNS | Statement: [.name, dnsProtocol, DNS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dnsProtocol Context triple: [.name, dnsProtocol, DNS]
-
A.
DNS
Indicates a relationship where one entity serves as or is associated with a Domain Name System (DNS) configuration or service for another entity, enabling the translation of domain names to network addresses.
-
B.
networkProtocolDomain
Indicates the network protocol or protocol family within which a given communication, service, or interaction operates.
-
C.
protocolName
chosen
Indicates the specific communication or interaction protocol used or associated with an entity or connection.
-
D.
DNAType
Indicates that one entity specifies, classifies, or represents the type or category of DNA associated with another entity.
-
E.
DNSZone
Indicates a relationship where a set of DNS records is grouped and managed together under a specific domain namespace as a single administrative unit.
- 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.