Triple
T21530542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Domain Name Dispute Resolution Centre |
E531214
|
entity |
| Predicate | handlesDisputesUnder |
P6660
|
FINISHED |
| Object | Uniform Domain Name Dispute Resolution Policy |
—
|
NE NERFINISHED |
How this triple was built (3 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: Uniform Domain Name Dispute Resolution Policy | Statement: [Asian Domain Name Dispute Resolution Centre, handlesDisputesUnder, Uniform Domain Name Dispute Resolution Policy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uniform Domain Name Dispute Resolution Policy Context triple: [Asian Domain Name Dispute Resolution Centre, handlesDisputesUnder, Uniform Domain Name Dispute Resolution Policy]
-
A.
Uniform Domain Name Dispute Resolution Policy
chosen
The Uniform Domain Name Dispute Resolution Policy is an international administrative procedure established by ICANN to resolve disputes over abusive domain name registrations, such as cybersquatting, outside of traditional court litigation.
-
B.
WIPO Arbitration Rules
The WIPO Arbitration Rules are a specialized set of procedures designed for resolving intellectual property and technology disputes through arbitration under the auspices of the World Intellectual Property Organization.
-
C.
Asian Domain Name Dispute Resolution Centre
The Asian Domain Name Dispute Resolution Centre is an approved dispute resolution service provider that handles domain name conflicts, particularly involving .asia and other domains, under ICANN’s Uniform Domain Name Dispute Resolution Policy.
-
D.
ICANN community consensus policies
ICANN community consensus policies are collaboratively developed rules and standards created by the global Internet community to guide how domain names and related registration data are managed across the Domain Name System.
-
E.
GNSO
The GNSO (Generic Names Supporting Organization) is a key policy-development body within ICANN responsible for creating and managing policies related to generic top-level domains (gTLDs) on the internet.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesDisputesUnder Context triple: [Asian Domain Name Dispute Resolution Centre, handlesDisputesUnder, Uniform Domain Name Dispute Resolution Policy]
-
A.
handlesDisputesOver
chosen
Indicates that one entity is responsible for managing, resolving, or adjudicating disputes concerning another entity.
-
B.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
C.
hasDisputeRegime
Indicates that there exists a specific dispute-handling framework, system, or set of rules governing how disputes related to the subject are managed or resolved.
-
D.
hasDisputeType
Indicates that an entity is associated with a particular category or type of dispute.
-
E.
disputeResolvedBy
Indicates that a particular dispute or conflict has been settled or resolved through the actions, decision, or intervention of a specified party or process.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d08ebf881909574e098404f93fa |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.