Triple
T9767696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .net |
E237037
|
entity |
| Predicate | supportsDnssec |
P19620
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [.net, supportsDnssec, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDnssec Context triple: [.net, supportsDnssec, true]
-
A.
DNSSECSupported
chosen
Indicates that a domain or DNS service supports and correctly implements DNSSEC security extensions for authenticating DNS data.
-
B.
IDNSupport
Indicates that an entity provides or enables support for Internationalized Domain Names (IDNs), such as registering, resolving, or handling domain names with non-ASCII characters.
-
C.
supportsOCSPStapling
Indicates that one entity enables or is compatible with OCSP stapling for validating the status of digital certificates in its interactions with another entity.
-
D.
rootZoneSigned
Indicates that the DNS root zone has been cryptographically signed, typically using DNSSEC, to provide data integrity and authentication.
-
E.
ICANNApproved
Indicates that an entity (such as a domain, registrar, or policy) has been formally reviewed and granted approval by ICANN, the Internet Corporation for Assigned Names and Numbers.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a2da648190836916a45d2998d7 |
completed | April 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.