Triple
T34946714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Privacy Act 1988 |
E1007873
|
entity |
| Predicate | introducedNotifiableDataBreachScheme |
P92231
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Privacy Act 1988, introducedNotifiableDataBreachScheme, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedNotifiableDataBreachScheme Context triple: [Privacy Act 1988, introducedNotifiableDataBreachScheme, true]
-
A.
hasBreaches
Indicates that one entity experiences, contains, or is affected by one or more security, structural, or policy breaches associated with another entity.
-
B.
mayBeBreachBy
Indicates that something has the potential to constitute a breach committed by a specified party.
-
C.
compromisedOn
Indicates that two or more parties reached a mutual agreement by each conceding or adjusting their original positions.
-
D.
policyIntroduced
chosen
Indicates that a specific policy has been formally brought into effect or announced by an authority or organization.
-
E.
notableProtectiveIncident
Indicates that a significant event occurred in which one entity protected or defended another in a notable or remarkable way.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4 p.m.