Triple
T793437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAO Council |
E16965
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FAO organ |
C3094
|
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: FAO organ Context triple: [FAO Council, instanceOf, FAO organ]
-
A.
UN administrative body
A UN administrative body is an organizational entity within the United Nations responsible for managing, coordinating, and implementing the day-to-day operations, policies, and programs mandated by UN organs and agreements.
-
B.
administrative organ of an international organization
chosen
An administrative organ of an international organization is a permanent body responsible for managing the organization’s day-to-day operations, implementing its decisions, and providing support services to its other organs and member states.
-
C.
organ of the Organization of American States
An organ of the Organization of American States is an official institutional body established by the OAS Charter to perform specific functions—such as political, judicial, administrative, or advisory roles—in support of the organization’s purposes and decision-making processes.
-
D.
principal organ of UNESCO
The principal organ of UNESCO is a primary governing body responsible for setting the organization’s policies, strategic direction, and overall programmatic priorities.
-
E.
organ of the League of Nations
An organ of the League of Nations is an institutional body established by the League to perform specific functions such as decision-making, administration, or dispute resolution within the organization’s international governance framework.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:38 p.m.