Triple
T13968925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merit Network |
E336000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional research and education network |
C497
|
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: regional research and education network Context triple: [Merit Network, instanceOf, regional research and education network]
-
A.
regional collaborative network
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
-
B.
regional institute
A regional institute is an organization dedicated to education, research, or specialized services that primarily serves and addresses the needs of a specific geographic area or region.
-
C.
research network
chosen
A research network is a structured system of interconnected researchers, institutions, and resources that collaboratively generate, share, and advance knowledge within and across disciplines.
-
D.
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.
-
E.
Regional At-Large Organization
A Regional At-Large Organization is a geographically defined body that represents and coordinates the interests, participation, and activities of individual Internet users and At-Large Structures within a specific region in global Internet governance processes.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:18 p.m.