Triple
T21497095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard school of antitrust |
E530383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | approach to antitrust law |
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: approach to antitrust law Context triple: [Harvard school of antitrust, instanceOf, approach to antitrust law]
-
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.
competition law framework
A competition law framework is a structured set of legal rules, principles, and enforcement mechanisms designed to prevent anti-competitive practices, promote fair market behavior, and protect consumer welfare.
-
C.
competition law provision
A competition law provision is a legal rule or clause designed to regulate market behavior by preventing anti-competitive practices, promoting fair competition, and protecting consumer welfare.
-
D.
network of competition authorities
A network of competition authorities is a collaborative framework linking national or regional antitrust agencies to coordinate enforcement, share information, and promote consistent competition policy across jurisdictions.
-
E.
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.
- F. None of above. chosen
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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:23 p.m.