Triple
T26643464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT&T avoided immediate antitrust dissolution |
E668841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical antitrust outcome |
C17820
|
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: historical antitrust outcome Context triple: [AT&T avoided immediate antitrust dissolution, instanceOf, historical antitrust outcome]
-
A.
antitrust case
chosen
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.
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.
-
C.
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.
-
D.
approach to antitrust law
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.
-
E.
antitrust lawyer
An antitrust lawyer is a legal professional who specializes in laws and regulations that promote market competition and prevent anti-competitive practices such as monopolies, price-fixing, and unfair trade restraints.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:30 a.m.