Triple
T36637783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EES |
E904507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | border management information system |
C6282
|
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 management information system Context triple: [EES, instanceOf, border management information system]
-
A.
border control program
chosen
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 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.
-
C.
border security risk-management program category
A border security risk-management program category is a classification grouping that organizes and prioritizes related risks, controls, and initiatives for protecting national borders against threats such as illegal migration, smuggling, terrorism, and contraband.
-
D.
border post
A border post is an official checkpoint facility located at or near a national boundary where authorities control and monitor the movement of people, goods, and vehicles between countries.
-
E.
international border system
An international border system is the coordinated set of legal frameworks, physical infrastructures, technologies, and administrative processes that regulate the movement of people, goods, and information between sovereign states.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.