Triple
T26688839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branch 227 (Damascus region branch) |
E672820
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syrian military intelligence branch |
C29286
|
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: Syrian military intelligence branch Context triple: [Branch 227 (Damascus region branch), instanceOf, Syrian military intelligence branch]
-
A.
Inter-Services Intelligence
Inter-Services Intelligence is Pakistan’s premier military-operated intelligence agency responsible for gathering, analyzing, and acting on domestic and foreign intelligence to support national security and strategic objectives.
-
B.
Lebanese militia
A Lebanese militia is an organized, often ideologically or sectarian-based armed group operating within or from Lebanon, typically outside full state control and engaged in political, security, or military activities.
-
C.
Syrian government body
chosen
A Syrian government body is an official organization or institution established by the Syrian state to administer public policy, provide services, and enforce laws within its jurisdiction.
-
D.
Syrian Air Force base
A Syrian Air Force base is a military installation in Syria that supports air operations through the housing, maintenance, and deployment of aircraft, personnel, and related infrastructure.
-
E.
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.
- F. None of above.
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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:24 a.m.