Triple
T18050188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO communication and information programmes |
E431909
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | knowledge society initiative |
C39758
|
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: knowledge society initiative Context triple: [UNESCO communication and information programmes, instanceOf, knowledge society initiative]
-
A.
Knowledge and Innovation Community
A Knowledge and Innovation Community is an ecosystem that brings together academic, industrial, and entrepreneurial actors to collaboratively generate, share, and apply knowledge for innovative solutions and sustainable economic and social impact.
-
B.
learned society
A learned society is an organization that exists to promote an academic discipline or group of related disciplines through research, communication, and professional collaboration among scholars and practitioners.
-
C.
open knowledge program
An open knowledge program is an initiative designed to create, share, and maintain freely accessible, collaboratively developed information resources for public use and learning.
-
D.
open knowledge organization
An open knowledge organization is a collaborative, transparent system for structuring, connecting, and sharing information that allows broad participation in creating, maintaining, and reusing knowledge resources.
-
E.
knowledge hub
A knowledge hub is a centralized platform or environment where information, expertise, and resources are collected, organized, and shared to support learning, collaboration, and informed decision-making.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:25 a.m.