Triple
T30350814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .info |
E771982
|
entity |
| Predicate | supportsNameServers |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNameServers Context triple: [.info, supportsNameServers, yes]
-
A.
supportsNameserversAbroad
Indicates that an entity provides or allows the use of nameservers located in foreign or cross-border jurisdictions.
-
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.
supportsRDAP
Indicates that one entity provides or is compatible with RDAP (Registration Data Access Protocol) functionality for another entity.
-
D.
supportsNameType
Indicates that one entity is capable of handling, recognizing, or being associated with a particular type or category of name.
-
E.
supportsWHOIS
Indicates that one entity provides or is compatible with WHOIS lookup functionality for another entity.
- F. None of above. chosen
Provenance (1 batch)
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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:56 p.m.