Triple
T25027804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli law |
E626756
|
entity |
| Predicate | hasReligiousCourtsFor |
P139668
|
FINISHED |
| Object | Jewish community |
—
|
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: Jewish community | Statement: [Israeli law, hasReligiousCourtsFor, Jewish community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousCourtsFor Context triple: [Israeli law, hasReligiousCourtsFor, Jewish community]
-
A.
religionOfCourt
Indicates the religious affiliation associated with a particular court.
-
B.
religiousCourtsJurisdiction
chosen
Indicates that religious courts have legal authority or decision-making power over certain matters or individuals.
-
C.
religiousJurisdiction
Indicates that one entity holds official religious authority or governance over another entity or area.
-
D.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
E.
hasDefendantReligion
Indicates that a specified religion is the religious affiliation of the defendant in a legal case.
- 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_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 18, 2026, 6:07 a.m.