Triple
T16703207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OECD Global Forum on Competition |
E405899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | competition policy platform |
C38262
|
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: competition policy platform Context triple: [OECD Global Forum on Competition, instanceOf, competition policy platform]
-
A.
competition policy
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.
-
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.
international competition
An international competition is a structured event in which individuals or teams from multiple countries compete under standardized rules to determine relative excellence in a specific field or activity.
-
D.
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.
-
E.
commercial rivalry
Commercial rivalry is the competitive relationship between businesses striving to outperform each other in market share, profitability, and customer loyalty through strategies such as pricing, innovation, marketing, and differentiation.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.