Triple
T19901228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Lebanon security zone |
E478293
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | militarized buffer zone |
C16458
|
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: militarized buffer zone Context triple: [South Lebanon security zone, instanceOf, militarized buffer zone]
-
A.
militarized boundary
A militarized boundary is a heavily fortified and closely monitored border between political entities, characterized by the presence or threat of military force to control movement and enforce territorial claims.
-
B.
military-controlled zone
chosen
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
-
C.
border troops
Border troops are specialized military or paramilitary forces responsible for monitoring, securing, and defending a nation's borders against illegal crossings, smuggling, and external threats.
-
D.
demilitarized zone arrangement
A demilitarized zone arrangement is a structured agreement or configuration that establishes a buffer area where military forces, weapons, or hostile activities are restricted or prohibited to reduce conflict and enhance security between opposing parties.
-
E.
border conflict
A border conflict is a dispute between neighboring states or groups over the ownership, control, or demarcation of a shared territorial boundary.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:52 p.m.