Triple
T7948611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | regular session of the United Nations General Assembly |
E184557
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | recurring international diplomatic event |
C11846
|
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: recurring international diplomatic event Context triple: [regular session of the United Nations General Assembly, instanceOf, recurring international diplomatic event]
-
A.
recurring quadrennial event
A recurring quadrennial event is an occurrence or series of activities that is scheduled to take place once every four years on a regular, repeating basis.
-
B.
diplomatic conference
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
C.
diplomatic incident
A diplomatic incident is an event or action involving representatives of different states that causes tension, conflict, or embarrassment in their official relations.
-
D.
international political forum
chosen
An international political forum is a structured platform where representatives from multiple countries convene to discuss, negotiate, and coordinate on global political, economic, and security issues.
-
E.
diplomatic initiative
A diplomatic initiative is a coordinated effort by one or more states or international actors to open, advance, or resolve political, economic, or security issues through negotiation and dialogue rather than coercion or conflict.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:10 p.m.