Triple
T22675332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rule of reason |
E560329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | antitrust legal doctrine |
C44875
|
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: antitrust legal doctrine Context triple: [rule of reason, instanceOf, antitrust legal doctrine]
-
A.
antitrust case
An antitrust case is a legal action in which government agencies or private parties challenge business practices alleged to unlawfully restrict competition, create monopolies, or otherwise violate competition laws.
-
B.
approach to antitrust law
chosen
An approach to antitrust law is a conceptual framework that guides how competition rules are interpreted, enforced, and balanced against other policy goals such as innovation, consumer welfare, and market fairness.
-
C.
antitrust report
An antitrust report is a formal document that analyzes market structures, business practices, and competitive effects to assess potential violations of competition laws and recommend regulatory or legal actions.
-
D.
antitrust agreement
An antitrust agreement is a formal or informal arrangement between two or more independent economic entities that coordinates their competitive behavior in a way that may restrict competition, such as fixing prices, limiting output, or dividing markets.
-
E.
antitrust enforcer
An antitrust enforcer is an authority or official responsible for investigating, preventing, and remedying anti-competitive practices to protect market competition and consumer welfare.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:11 p.m.