Triple
T34407124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | חוק השבות |
E883145
|
entity |
| Predicate | hasBeenReviewedBy |
P1394
|
FINISHED |
| Object | בית המשפט העליון בישראל |
—
|
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: בית המשפט העליון בישראל | Statement: [חוק השבות, hasBeenReviewedBy, בית המשפט העליון בישראל]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenReviewedBy Context triple: [חוק השבות, hasBeenReviewedBy, בית המשפט העליון בישראל]
-
A.
hasBeenReviewedIn
Indicates that an entity has been evaluated or critiqued within a specific review, publication, or reviewing context.
-
B.
hasReviewed
Indicates that one entity has examined, evaluated, or provided feedback on another entity (such as a work, product, or performance).
-
C.
isReviewedAfter
Indicates that one entity’s review occurs later in time than another entity’s review.
-
D.
reviewedBy
chosen
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
E.
reviewedAs
Indicates that one entity has evaluated, critiqued, or assessed another entity in a particular capacity, role, or context.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:59 a.m.