Triple
T21497096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard school of antitrust |
E530383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | approach to competition policy |
C7865
|
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 competition policy Context triple: [Harvard school of antitrust, instanceOf, approach to competition policy]
-
A.
competition policy assessment
Competition policy assessment is the systematic evaluation of laws, regulations, and market conditions to determine their impact on market competition, consumer welfare, and economic efficiency.
-
B.
competition policy
chosen
Competition policy is the set of laws, regulations, and enforcement practices designed to promote fair market competition, prevent anti-competitive behavior, and protect consumer welfare.
-
C.
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.
-
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.
competition policy platform
A competition policy platform is a digital system that centralizes tools, data, and workflows to design, analyze, and enforce rules that promote fair market competition and prevent anti-competitive behavior.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:23 p.m.