Triple
T25640561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whistleblower Protection Act |
E642825
|
entity |
| Predicate | coversDisclosureOf |
P162894
|
FINISHED |
| Object | abuse of authority |
—
|
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: abuse of authority | Statement: [Whistleblower Protection Act, coversDisclosureOf, abuse of authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversDisclosureOf Context triple: [Whistleblower Protection Act, coversDisclosureOf, abuse of authority]
-
A.
coversDisclosureOf
chosen
Indicates that one entity’s scope, terms, or provisions include and apply to the act or content of another entity’s disclosure.
-
B.
discloses
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
-
C.
typeOfDisclosure
Indicates the specific category or nature of a disclosure made in a given context (e.g., legal, financial, personal).
-
D.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
-
E.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 5:41 p.m.