Triple
T177002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Knowledge Foundation |
E3594
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open data advocacy organization |
C6
|
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: open data advocacy organization Context triple: [Open Knowledge Foundation, instanceOf, open data advocacy organization]
-
A.
nonprofit organization
chosen
A nonprofit organization is an entity formed for purposes other than generating profit, using any surplus revenues to further its mission or public benefit rather than distributing them to owners or shareholders.
-
B.
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.
-
C.
open content
Open content is any creative work that is freely accessible, usable, modifiable, and shareable by anyone, typically under an open license that grants these permissions.
-
D.
open content license
An open content license is a legal framework that allows creators to grant the public permission to use, share, and often modify their work under specified conditions, typically to promote free access and collaboration.
-
E.
research organization
A research organization is an institution that systematically investigates specific questions or problems to generate new knowledge, technologies, or insights, often within scientific, academic, or applied domains.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.