Triple
T33512403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Competition Network |
E858283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | competition law enforcement 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 law enforcement network Context triple: [European Competition Network, instanceOf, competition law enforcement 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 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.
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.
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.
antitrust enforcement regulation
Antitrust enforcement regulation is the body of laws, policies, and procedures through which governments prevent, investigate, and remedy anti-competitive business practices to protect market competition and consumer welfare.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.