Triple
T5679311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union at CELAC–EU summits |
E125161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | participant in multilateral summitry |
C15892
|
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: participant in multilateral summitry Context triple: [European Union at CELAC–EU summits, instanceOf, participant in multilateral summitry]
-
A.
G7 participant
A G7 participant is a state or entity that takes part in the Group of Seven’s intergovernmental discussions and decision-making processes on global economic, political, and security issues.
-
B.
G20 participant
A G20 participant is a state or regional organization that takes part in the Group of Twenty’s international economic and financial policy discussions, summits, and cooperative initiatives.
-
C.
multilateral negotiation process
A multilateral negotiation process is a structured series of interactions among three or more parties with differing interests, aimed at reaching mutually acceptable agreements through communication, bargaining, and compromise.
-
D.
participants in international initiative
chosen
Individuals, organizations, or states that actively engage in and contribute resources, expertise, or decision-making to a coordinated effort addressing issues of shared international concern.
-
E.
multinational military forum
A multinational military forum is an organized platform where representatives from multiple countries' armed forces convene to discuss security issues, coordinate policies, share best practices, and enhance mutual understanding and cooperation.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:44 p.m.