Triple
T740658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Radiocommunication Conference |
E15235
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Nations conference |
C2126
|
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: United Nations conference Context triple: [World Radiocommunication Conference, instanceOf, United Nations conference]
-
A.
United Nations intergovernmental process
chosen
The United Nations intergovernmental process is the formal, member state–driven system of negotiations, decision-making, and norm-setting through which UN bodies develop, adopt, and implement international agreements, resolutions, and policies.
-
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.
World War II conference
A World War II conference is a high-level diplomatic meeting held among Allied or Axis leaders during the war to coordinate military strategy, negotiate political arrangements, and shape postwar plans.
-
D.
United Nations role
The "United Nations role" conceptual class represents the specific function, responsibility, or position an entity holds within the UN system, such as mediator, peacekeeper, observer, or member state.
-
E.
United Nations resolution
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.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.