Triple
T31622031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Definition of Aggression |
E806921
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNGA Resolution |
C744
|
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: UNGA Resolution Context triple: [Definition of Aggression, instanceOf, UNGA Resolution]
-
A.
United Nations resolution
chosen
A United Nations resolution is a formal text adopted by a UN organ that expresses decisions, recommendations, or positions on international issues, guiding member states’ actions and the organization’s activities.
-
B.
United Nations General Assembly agenda item
A United Nations General Assembly agenda item is a specific topic or issue formally listed for consideration, discussion, and possible action by the General Assembly during its sessions.
-
C.
United Nations outcome document
A United Nations outcome document is a formal, negotiated text adopted by UN member states that records agreed conclusions, commitments, and recommended actions resulting from a UN conference, summit, or meeting.
-
D.
United Nations proposal
A United Nations proposal is a formal document submitted by member states or UN bodies that outlines recommended actions, policies, or resolutions for consideration, negotiation, and potential adoption by UN organs.
-
E.
United Nations General Assembly session
A United Nations General Assembly session is a formal gathering of all UN member states convened to debate, negotiate, and adopt resolutions on global issues within the Assembly’s mandate.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:41 p.m.