Triple
T32518904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN Registry Agreement |
E831130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | registry agreement |
C61558
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: registry agreement Context triple: [ICANN Registry Agreement, instanceOf, registry agreement]
-
A.
association agreement
An association agreement is a formal contract that defines the rights, responsibilities, and collaborative arrangements between two or more parties forming an ongoing relationship, often within a professional, organizational, or international context.
-
B.
association agreement component
An association agreement component is a modular element within a broader agreement that defines specific terms, conditions, or relationships between associated parties or entities.
-
C.
headquarters agreement
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
-
D.
international agreement package
An international agreement package is a bundled set of formally negotiated documents, terms, and supporting materials that collectively define and govern a cross-border accord between participating entities or nations.
-
E.
registration authority
A registration authority is an entity responsible for verifying the identity and eligibility of subjects and approving or managing their registration within a specified system or domain.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.