Triple
T7779617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU–US Privacy Shield |
E221479
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU–US data protection arrangement |
C14089
|
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: EU–US data protection arrangement Context triple: [EU–US Privacy Shield, instanceOf, EU–US data protection arrangement]
-
A.
USA FREEDOM Act
The USA FREEDOM Act is a U.S. law enacted in 2015 that reforms government surveillance authorities by limiting bulk data collection and increasing transparency and oversight of intelligence activities.
-
B.
component of Eurojust
A component of Eurojust is an organizational unit or structural element within the Eurojust agency that contributes to its mission of coordinating judicial cooperation in criminal matters among EU member states.
-
C.
U.S. government encryption standard
A U.S. government encryption standard is an officially approved cryptographic algorithm or protocol, such as AES, mandated or recommended by federal authorities to protect sensitive government and public-sector information.
-
D.
EU legal act
chosen
An EU legal act is a binding or non-binding instrument adopted by the European Union’s institutions—such as regulations, directives, decisions, recommendations, or opinions—to create, modify, or guide the application of law within the EU legal order.
-
E.
network of competition authorities
A network of competition authorities is a collaborative framework linking national or regional antitrust agencies to coordinate enforcement, share information, and promote consistent competition policy across jurisdictions.
- 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 4:19 p.m.