Triple
T7948559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN General Assembly resolution 377 A (V) |
E184556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Uniting for Peace 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: Uniting for Peace resolution Context triple: [UN General Assembly resolution 377 A (V), instanceOf, Uniting for Peace 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 hearing
A United Nations hearing is a formal session in which UN member states, experts, and stakeholders present information, debate issues, and provide testimony to inform international decision-making and policy development.
-
C.
mission to the United Nations
A mission to the United Nations is a permanent diplomatic representation of a member state or observer entity to the UN, responsible for managing its participation, negotiations, and interests within the organization.
-
D.
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.
-
E.
division of the United Nations
A division of the United Nations is an organizational unit within the UN system responsible for carrying out specialized functions, programs, or administrative tasks in support of the organization's overarching goals and mandates.
- 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.