Triple
T10341330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Competition Network |
E243133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | competition authority network |
C19623
|
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 authority network Context triple: [European Competition Network, instanceOf, competition authority network]
-
A.
network of competition authorities
chosen
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.
-
B.
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.
-
C.
combined authority
A combined authority is a legal entity formed by two or more local government areas that collaborate to exercise shared strategic powers and responsibilities, typically over transport, economic development, and regional planning.
-
D.
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.
-
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.
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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:55 a.m.