Triple
T10625506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | False Claims Act |
E250310
|
entity |
| Predicate | usedHeavilyIn |
P11801
|
FINISHED |
| Object | health care enforcement |
—
|
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: health care enforcement | Statement: [False Claims Act, usedHeavilyIn, health care enforcement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHeavilyIn Context triple: [False Claims Act, usedHeavilyIn, health care enforcement]
-
A.
widelyUsedIn
chosen
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
B.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
D.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_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. |
Created at: April 8, 2026, 8:54 p.m.