Triple
T33074036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planning Directorate (IDF) |
E846310
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | directorate of the Israel Defense Forces |
C59529
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: directorate of the Israel Defense Forces Context triple: [Planning Directorate (IDF), instanceOf, directorate of the Israel Defense Forces]
-
A.
כוח ביטחון ישראלי
כוח ביטחון ישראלי הוא גוף ממלכתי או רשמי הפועל מטעם מדינת ישראל לשמירה על ביטחון המדינה, אזרחיה ושטחיה באמצעות אכיפת חוק, הגנה, מודיעין ופעילות מבצעית.
-
B.
Israel Defense Forces unit
An Israel Defense Forces unit is an organized military formation within the IDF, composed of personnel and equipment structured to perform specific operational, support, or administrative missions in defense of the State of Israel.
-
C.
Israel Defense Forces brigade
An Israel Defense Forces brigade is a mid-level military formation typically composed of several battalions, integrating combat, support, and command elements to conduct coordinated operations within a defined mission area.
-
D.
Israeli military brigade
An Israeli military brigade is a mid-sized, combined-arms combat formation within the Israel Defense Forces, typically composed of several battalions and supporting units organized to conduct coordinated offensive and defensive operations.
-
E.
Israeli military commander
An Israeli military commander is a high-ranking officer responsible for planning, directing, and overseeing Israel Defense Forces operations, strategy, and personnel in defense of the State of Israel.
- F. None of above. chosen
Provenance (1 batch)
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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:25 a.m.