Triple
T33558949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU Single Market governance framework |
E859560
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory governance system |
C56522
|
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: regulatory governance system Context triple: [EU Single Market governance framework, instanceOf, regulatory governance system]
-
A.
regulatory system
chosen
A regulatory system is a coordinated set of mechanisms, rules, and processes designed to monitor, control, and adjust the behavior of a system to maintain stability, compliance, or desired performance.
-
B.
regulatory framework
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
C.
administrative oversight regime
An administrative oversight regime is a structured system of rules, procedures, and institutions designed to monitor, review, and correct the actions and decisions of administrative bodies to ensure legality, accountability, and fairness.
-
D.
governance doctrine
A governance doctrine is a coherent set of principles, rules, and practices that defines how authority is structured, decisions are made, and accountability is maintained within an organization or political system.
-
E.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.