Triple
T2100369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Integrated Technical Cooperation Programme |
E37078
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technical cooperation programme |
C2063
|
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: technical cooperation programme Context triple: [Integrated Technical Cooperation Programme, instanceOf, technical cooperation programme]
-
A.
intergovernmental programme
An intergovernmental programme is a coordinated set of policies, activities, or initiatives jointly designed, funded, and implemented by multiple governments or international organizations to address shared issues or achieve common goals across borders.
-
B.
international cooperation mechanism
chosen
An international cooperation mechanism is a structured framework, agreement, or institution through which multiple countries coordinate policies, share resources, and jointly address cross-border issues or common goals.
-
C.
technical code
Technical code is a structured set of machine-readable instructions, written in a specific programming language, that implements precise computational logic and system behavior according to defined technical requirements.
-
D.
technical report
A technical report is a structured document that presents methods, data, analysis, and conclusions about a specific technical or scientific investigation for a targeted audience.
-
E.
European Union education and training program component
A European Union education and training program component is a specific initiative, module, or activity designed and funded within an EU framework to support learning, skills development, and mobility objectives for targeted participants.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:43 p.m.