Triple
T2498293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pact for Research and Innovation in Europe |
E52402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intergovernmental agreement |
C824
|
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: intergovernmental agreement Context triple: [Pact for Research and Innovation in Europe, instanceOf, intergovernmental agreement]
-
A.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
B.
international agreement implementation area
The international agreement implementation area is a defined domain—such as a sector, region, or policy field—within which the provisions of an international agreement are applied, monitored, and enforced.
-
C.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
D.
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.
-
E.
political agreement
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:46 p.m.