Triple
T35849908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | שב"כ |
E1036318
|
entity |
| Predicate | סמכות_חוקית |
P65906
|
FINISHED |
| Object | חוק שירות הביטחון הכללי |
—
|
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: חוק שירות הביטחון הכללי | Statement: [שב"כ, סמכות_חוקית, חוק שירות הביטחון הכללי]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: סמכות_חוקית Context triple: [שב"כ, סמכות_חוקית, חוק שירות הביטחון הכללי]
-
A.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
B.
lawCollection
Indicates a relationship in which a set of legal rules, statutes, or regulations is grouped or organized together as a collection.
-
C.
lawLibrary
Indicates a relationship where a location or resource functions as a library specifically dedicated to legal materials, services, or research.
-
D.
majorLegalSource
chosen
Indicates that one entity serves as a primary or authoritative legal basis or reference for another entity.
-
E.
legalMatters
Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.