Triple
T17383590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | שירות הביטחון הכללי |
E422629
|
entity |
| Predicate | מעמד_משפטי |
P127283
|
FINISHED |
| Object | כפוף לחוק שירות הביטחון הכללי |
—
|
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: כפוף לחוק שירות הביטחון הכללי | Statement: [שירות הביטחון הכללי, מעמד_משפטי, כפוף לחוק שירות הביטחון הכללי]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: מעמד_משפטי Context triple: [שירות הביטחון הכללי, מעמד_משפטי, כפוף לחוק שירות הביטחון הכללי]
-
A.
يحكمها
Indicates that an entity governs, rules, or exercises authority over another entity.
-
B.
סיבת זכייה
Indicates the reason or cause for which an entity wins or is awarded something.
-
C.
marriageResolvedBy
Indicates that a marital relationship between two parties has been formally concluded or dissolved through a specific resolving action or process (e.g., divorce, annulment).
-
D.
marriageFormedBy
Indicates that a marriage relationship was created or brought into existence by a specific event, action, or process.
-
E.
ייחוס
Indicates an attribution or assignment relationship, where a property, role, or characteristic is ascribed from one entity to another.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a87d9948190986021f1fb5a4e00 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.