Triple
T26002488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palestinian Central Council |
E646667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | PLO governing body |
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: PLO governing body Context triple: [Palestinian Central Council, instanceOf, PLO governing body]
-
A.
Arab League body
An Arab League body is an institutional organ or agency established by the League of Arab States to carry out specific political, economic, social, cultural, or administrative functions on behalf of its member states.
-
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.
principal organ of the Arab League
The principal organ of the Arab League is the Council of the League, composed of representatives of member states, which serves as the main decision-making body responsible for coordinating policies and actions among its members.
-
D.
Palestinian political organization
A Palestinian political organization is a structured group that represents and advocates for the political interests, rights, and self-determination of Palestinians through governance, diplomacy, activism, or resistance.
-
E.
Lebanese political organization
A Lebanese political organization is a structured group operating within Lebanon’s political system that seeks to influence governance, policy, and public opinion through formal or informal participation in political processes.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9 a.m.