Triple
T25717608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmony programme |
E644901
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear energy advocacy initiative |
C29148
|
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: nuclear energy advocacy initiative Context triple: [Harmony programme, instanceOf, nuclear energy advocacy initiative]
-
A.
national nuclear energy program
A national nuclear energy program is a coordinated governmental initiative that plans, develops, regulates, and operates nuclear technologies to generate electricity and support related industrial, scientific, and security objectives.
-
B.
energy cooperation initiative
An energy cooperation initiative is a coordinated effort among multiple stakeholders—such as governments, organizations, or communities—to jointly develop, share, and manage energy resources, technologies, and policies for mutual benefit and sustainability.
-
C.
advocacy initiative
chosen
An advocacy initiative is a coordinated effort or campaign designed to influence public opinion, policy, or institutional practices in support of a specific cause or group.
-
D.
nuclear energy law
Nuclear energy law is the body of legal rules, regulations, and international agreements that govern the safe, secure, and peaceful use, regulation, and oversight of nuclear materials, facilities, and activities.
-
E.
nuclear reactor project
A nuclear reactor project is a coordinated engineering and management effort to design, license, construct, operate, and eventually decommission a nuclear reactor facility for energy production, research, or other specialized applications.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 9:46 p.m.