Triple
T13016840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verification Annex of the Chemical Weapons Convention |
E322574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | verification regime |
C5267
|
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: verification regime Context triple: [Verification Annex of the Chemical Weapons Convention, instanceOf, verification regime]
-
A.
identity verification platform
An identity verification platform is a system that securely validates and authenticates individuals’ identities using documents, biometrics, and data checks to prevent fraud and ensure trust in digital interactions.
-
B.
security checkpoint
A security checkpoint is a controlled access area where people, belongings, or vehicles are inspected to prevent unauthorized entry and ensure safety.
-
C.
visual certification company
A visual certification company is an organization that evaluates, verifies, and officially certifies the authenticity, quality, or compliance of visual content, designs, or visual-based products according to defined standards.
-
D.
administrative oversight regime
chosen
An administrative oversight regime is a structured system of rules, procedures, and institutions designed to monitor, review, and correct the actions and decisions of administrative bodies to ensure legality, accountability, and fairness.
-
E.
sanctions regime
A sanctions regime is a structured set of legal and policy measures—such as trade restrictions, asset freezes, and travel bans—imposed by one or more actors to coerce, deter, or punish targeted states, entities, or individuals.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:51 p.m.