Triple
T26025309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allon Plan |
E647273
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Israeli political plan |
C34443
|
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: Israeli political plan Context triple: [Allon Plan, instanceOf, Israeli political plan]
-
A.
Israeli government policy
chosen
Israeli government policy encompasses the strategic, legal, economic, and security decisions and frameworks established by Israel’s governing institutions to manage domestic affairs, regional relations, and international engagement.
-
B.
Israeli government
The Israeli government is the political authority of the State of Israel, comprising executive, legislative, and judicial branches that create, implement, and interpret laws while managing domestic and foreign affairs.
-
C.
political alliance in Israel
A political alliance in Israel is a temporary or long-term coalition of two or more political parties that join forces to contest elections, coordinate policy positions, and increase their collective influence in the Knesset and government formation.
-
D.
Mexican political plan
A Mexican political plan is a formal, often revolutionary, document that outlines a political movement’s principles, goals, and strategies for restructuring or challenging the existing government in Mexico.
-
E.
Zionist concept
A Zionist concept is an idea, principle, or belief related to the Jewish national movement advocating for the establishment, development, and security of a Jewish homeland in the historic Land of Israel.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:05 a.m.