Triple
T35736732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torah veAvodah |
E1032908
|
entity |
| Predicate | viewOnLandOfIsrael |
P34689
|
FINISHED |
| Object | settlement of the Land as a mitzvah |
—
|
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: settlement of the Land as a mitzvah | Statement: [Torah veAvodah, viewOnLandOfIsrael, settlement of the Land as a mitzvah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnLandOfIsrael Context triple: [Torah veAvodah, viewOnLandOfIsrael, settlement of the Land as a mitzvah]
-
A.
viewOnIsrael
chosen
Indicates a stance, opinion, or perspective that an entity holds regarding Israel.
-
B.
viewOfJerusalem
Indicates that something depicts, presents, or provides a visual representation or perspective of Jerusalem.
-
C.
viewOnZionism
Indicates a stance, opinion, or attitude that an entity holds toward Zionism.
-
D.
judaismView
Indicates a relationship where one entity holds a particular view, interpretation, or doctrinal position within or about Judaism regarding another entity or topic.
-
E.
positionOnJerusalem
Indicates that one entity occupies or is located at a specific position within the area of Jerusalem.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.