Triple
T25027811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli law |
E626756
|
entity |
| Predicate | hasCourtSystemLevel |
P71353
|
FINISHED |
| Object | magistrates’ courts |
—
|
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: magistrates’ courts | Statement: [Israeli law, hasCourtSystemLevel, magistrates’ courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtSystemLevel Context triple: [Israeli law, hasCourtSystemLevel, magistrates’ courts]
-
A.
hadCourtLevel
chosen
Indicates the specific hierarchical level of the court at which a legal case or judicial action took place.
-
B.
isPartOfCourtSystem
Indicates that one legal body, division, or component belongs to and operates within a larger court system.
-
C.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
D.
hasStateCourt
Indicates that a given jurisdiction or region possesses an official court that operates at the state level.
-
E.
hasJudicialPowerLevel
Indicates that an entity possesses a specified degree or extent of judicial authority or decision-making power.
- 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_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 18, 2026, 6:07 a.m.