Triple
T29052220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Resolute |
E735289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | border protection operation |
C54644
|
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: border protection operation Context triple: [Operation Resolute, instanceOf, border protection operation]
-
A.
border control program
A border control program is a coordinated set of policies, procedures, and technologies designed to regulate and monitor the movement of people and goods across a country's borders to ensure security, compliance, and lawful entry.
-
B.
border security legislation
Border security legislation comprises the laws and regulations that govern the control, monitoring, and protection of a nation's borders, including immigration enforcement, customs procedures, and measures to prevent illegal crossings and contraband.
-
C.
border control agency
A border control agency is a governmental organization responsible for regulating and monitoring the movement of people and goods across a country's borders to ensure security, compliance with laws, and protection of national interests.
-
D.
border defense system
A border defense system is an integrated network of physical barriers, surveillance technologies, personnel, and response protocols designed to monitor, control, and protect a nation's boundaries from unauthorized crossings and external threats.
-
E.
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.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:09 a.m.