Triple
T32292069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacDonald White Paper |
E824988
|
entity |
| Predicate | impactOnZionistPolicy |
P90352
|
FINISHED |
| Object | shift toward illegal immigration (Aliyah Bet) |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: shift toward illegal immigration (Aliyah Bet) | Statement: [MacDonald White Paper, impactOnZionistPolicy, shift toward illegal immigration (Aliyah Bet)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnZionistPolicy Context triple: [MacDonald White Paper, impactOnZionistPolicy, shift toward illegal immigration (Aliyah Bet)]
-
A.
effectOnZionism
chosen
Indicates how something influences, shapes, or impacts Zionism as an ideology, movement, or set of practices.
-
B.
viewOnZionism
Indicates a stance, opinion, or attitude that an entity holds toward Zionism.
-
C.
hasViewOnZionism
Indicates that an entity holds a particular opinion, stance, or perspective regarding Zionism.
-
D.
effectOnYishuv
Indicates the impact or consequences that an action, event, or condition has on the Yishuv (the Jewish community or settlement).
-
E.
typeOfZionism
Indicates the specific form or variant of Zionism that characterizes or is associated with a given entity.
- F. None of above.
Provenance (3 batches)
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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 12:44 a.m.