Triple
T25027842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli law |
E626756
|
entity |
| Predicate | permitsPetitionsTo |
P138408
|
FINISHED |
| Object | High Court of Justice (as part of Supreme Court) |
—
|
NE NERFINISHED |
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: High Court of Justice (as part of Supreme Court) | Statement: [Israeli law, permitsPetitionsTo, High Court of Justice (as part of Supreme Court)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitsPetitionsTo Context triple: [Israeli law, permitsPetitionsTo, High Court of Justice (as part of Supreme Court)]
-
A.
canBePetitionedBy
Indicates that an entity is eligible to receive formal petitions, requests, or appeals from another entity.
-
B.
containsPetition
Indicates that one entity includes or holds a petition within it, either as content or as a component.
-
C.
numberOfPetitions
Indicates the total count of petitions associated with a given entity or context.
-
D.
permitsFilingIn
chosen
Indicates that one entity authorizes or allows another entity to submit or initiate a filing within its jurisdiction, system, or process.
-
E.
partyTypePetitioners
Indicates that the associated parties in a legal case are classified as petitioners.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44f6c0538819084ae65fed91c4c86 |
completed | May 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:07 a.m.