Triple
T9002380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Solutions, LLC |
E215066
|
entity |
| Predicate | topLevelDomainSupported |
P52129
|
FINISHED |
| Object | .com |
—
|
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: .com | Statement: [Network Solutions, LLC, topLevelDomainSupported, .com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelDomainSupported Context triple: [Network Solutions, LLC, topLevelDomainSupported, .com]
-
A.
hasTopLevelDomain
chosen
Indicates that one entity (typically a website, domain name, or internet resource) is associated with a specific top-level domain (such as .com, .org, or .uk).
-
B.
regulatoryDomainSupported
Indicates that an entity is compatible with, and can operate under, a specified regulatory domain or jurisdiction.
-
C.
countryCodeTopLevelDomain
Indicates that a country is associated with a specific top-level internet domain code (ccTLD).
-
D.
TLDType
Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
-
E.
supportsCustomDomain
Indicates that an entity provides the capability to use or configure a custom domain name instead of a default or system-assigned domain.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6956a6e08190bd3853a7c1c130eb |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.