Triple
T12225563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Department of Justice antitrust litigation |
E291342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal criminal enforcement action |
C3764
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: federal criminal enforcement action Context triple: [U.S. Department of Justice antitrust litigation, instanceOf, federal criminal enforcement action]
-
A.
federal enforcement order
A federal enforcement order is a legally binding directive issued by a federal authority requiring specific actions or compliance to enforce federal laws, regulations, or judgments.
-
B.
federal investigation
A federal investigation is a formal inquiry conducted by national government agencies to gather evidence, determine whether federal laws have been violated, and support potential enforcement or prosecution actions.
-
C.
United States federal government action
chosen
A United States federal government action is any formal decision, policy, regulation, enforcement measure, or operation undertaken by a federal branch or agency under constitutional or statutory authority to influence public affairs or implement federal law.
-
D.
federal law
A federal law is a legally binding rule or statute enacted by a national government’s legislative body that applies uniformly across all states or regions within that nation.
-
E.
police operation
A police operation is a coordinated set of law enforcement activities planned and executed to prevent, investigate, or respond to criminal or public safety incidents.
- F. None of above.
Provenance (1 batch)
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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:51 p.m.