Triple
T4402089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lo Zeh Ha-Derekh |
E93641
|
entity |
| Predicate | positionWithinZionism |
P19558
|
FINISHED |
| Object | foundational text of Cultural Zionism |
—
|
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: foundational text of Cultural Zionism | Statement: [Lo Zeh Ha-Derekh, positionWithinZionism, foundational text of Cultural Zionism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinZionism Context triple: [Lo Zeh Ha-Derekh, positionWithinZionism, foundational text of Cultural Zionism]
-
A.
viewOnZionism
Indicates a stance, opinion, or attitude that an entity holds toward Zionism.
-
B.
hasViewOnZionism
Indicates that an entity holds a particular opinion, stance, or perspective regarding Zionism.
-
C.
placeInZionistHistory
chosen
Indicates that an entity holds a particular role, significance, or position within the historical development of Zionism.
-
D.
positionOnArabIsraeliConflict
Indicates a stance or viewpoint that an entity holds regarding the Arab–Israeli conflict.
-
E.
roleInIsrael
Indicates that an entity holds or held a specific role, position, or function within the context of Israel.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d08a0c8190ac6c125df40eca75 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.