Triple
T387956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Meteorological Congress |
E8818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | plenary organ of an international organization |
C172
|
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: plenary organ of an international organization Context triple: [World Meteorological Congress, instanceOf, plenary organ of an international organization]
-
A.
principal judicial organ of the United Nations
The principal judicial organ of the United Nations is the International Court of Justice, which settles legal disputes between states and gives advisory opinions on international legal questions in accordance with international law.
-
B.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
C.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
D.
legislative body
A legislative body is an organized group of elected or appointed representatives empowered to create, amend, and repeal laws and oversee government policy within a political system.
-
E.
advisory body
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.