Triple
T28554306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharia courts in Israel |
E722963
|
entity |
| Predicate | subjectToReviewOn |
P178291
|
FINISHED |
| Object | questions of jurisdiction |
—
|
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: questions of jurisdiction | Statement: [Sharia courts in Israel, subjectToReviewOn, questions of jurisdiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToReviewOn Context triple: [Sharia courts in Israel, subjectToReviewOn, questions of jurisdiction]
-
A.
subjectToReviewProcedure
Indicates that an entity is required to undergo a formal review process or procedure before a decision, approval, or action is finalized.
-
B.
reviewedFor
Indicates that one entity has examined or evaluated another entity for a specific purpose, standard, or context.
-
C.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
D.
hasBeenReviewedIn
Indicates that an entity has been evaluated or critiqued within a specific review, publication, or reviewing context.
-
E.
reviewedAs
Indicates that one entity has evaluated, critiqued, or assessed another entity in a particular capacity, role, or context.
- F. None of above. chosen
Provenance (4 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 28, 2026, 3:44 a.m.