Triple
T10625499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | False Claims Act |
E250310
|
entity |
| Predicate | whistleblowerTerm |
P95047
|
FINISHED |
| Object | relator |
—
|
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: relator | Statement: [False Claims Act, whistleblowerTerm, relator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: whistleblowerTerm Context triple: [False Claims Act, whistleblowerTerm, relator]
-
A.
notableWhistleblower
Indicates that the subject is recognized for having exposed significant wrongdoing or misconduct, typically within an organization or institution.
-
B.
usedSecretPolice
Indicates that an entity employed or relied on secret police forces to monitor, control, or repress others.
-
C.
conspirator
Indicates that an entity participates with others in planning or carrying out a secret or illicit scheme or action.
-
D.
employerSanctionsDescription
Indicates a description of penalties or disciplinary actions imposed by an employer in response to certain behaviors, violations, or conditions.
-
E.
threatensToReveal
Indicates a situation where one entity warns or intends to disclose information about another entity, typically to exert pressure or gain leverage.
- F. None of above. chosen
Provenance (4 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df80a30c81909f36fe221cf68822 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 8:54 p.m.