Triple
T29381891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Plus arrangements |
E745157
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | security agreement |
C3153
|
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: security agreement Context triple: [Berlin Plus arrangements, instanceOf, security agreement]
-
A.
security partnership
A security partnership is a collaborative relationship between organizations, agencies, or nations to share resources, information, and responsibilities for preventing, detecting, and responding to security threats.
-
B.
legal agreement
chosen
A legal agreement is a formally recognized arrangement between two or more parties that creates enforceable rights and obligations under the law.
-
C.
security exceptions clause
A security exceptions clause is a contractual provision that allows a party to deviate from or suspend certain obligations when necessary to protect its essential security interests, such as national security, cybersecurity, or the safety of critical infrastructure.
-
D.
security
Security is the conceptual class that encompasses mechanisms, policies, and practices designed to protect assets, information, and individuals from threats, vulnerabilities, and unauthorized access.
-
E.
shipping safety agreement
A shipping safety agreement is a formal contract between parties in the supply chain that defines responsibilities, standards, and procedures to prevent accidents, protect cargo, and ensure compliance with safety regulations during transportation.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:35 p.m.