Triple
T1798507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN Board |
E39659
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organ of ICANN |
C3094
|
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: organ of ICANN Context triple: [ICANN Board, instanceOf, organ of ICANN]
-
A.
Regional Internet Registry
A Regional Internet Registry is an organization responsible for allocating, registering, and managing Internet number resources (such as IP addresses and AS numbers) within a specific geographic region.
-
B.
domain name registry
A domain name registry is an authoritative database and management system that stores, maintains, and administers the records of all domain names registered under a specific top-level domain.
-
C.
administrative organ of an international organization
chosen
An administrative organ of an international organization is a permanent body responsible for managing the organization’s day-to-day operations, implementing its decisions, and providing support services to its other organs and member states.
-
D.
IETF working group
An IETF working group is a collaborative, time-bounded team of experts chartered within the Internet Engineering Task Force to develop, discuss, and standardize specific Internet technologies or protocols.
-
E.
multistakeholder organization
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
- F. None of above.
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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.