Triple
T7779649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU–US Privacy Shield |
E221479
|
entity |
| Predicate | wasInvalidatedBecauseOf |
P33292
|
FINISHED |
| Object | concerns about US surveillance laws |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: concerns about US surveillance laws | Statement: [EU–US Privacy Shield, wasInvalidatedBecauseOf, concerns about US surveillance laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInvalidatedBecauseOf Context triple: [EU–US Privacy Shield, wasInvalidatedBecauseOf, concerns about US surveillance laws]
-
A.
invalidated
chosen
Indicates that one entity has rendered another entity null, void, or no longer legally or logically effective.
-
B.
partiallyInvalidatedBy
Indicates that the validity or effect of something is reduced or weakened, but not completely nullified, by another action or entity.
-
C.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
D.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
E.
appliedBecauseOf
Indicates that one entity is applied, used, or enacted as a consequence or result of another specified cause or condition.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:19 p.m.