Triple
T8328911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Regulation (EC) No 2157/2001 |
E195026
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU company law instrument |
C6352
|
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: EU company law instrument Context triple: [Council Regulation (EC) No 2157/2001, instanceOf, EU company law instrument]
-
A.
EU legal act
An EU legal act is a binding or non-binding instrument adopted by the European Union’s institutions—such as regulations, directives, decisions, recommendations, or opinions—to create, modify, or guide the application of law within the EU legal order.
-
B.
legal entity form under European Union law
A legal entity form under European Union law is a standardized organizational structure, such as an SE or SCE, created by EU legislation to enable companies or associations to operate across member states under a unified legal framework.
-
C.
European Union regulation
chosen
A European Union regulation is a binding legislative act that applies directly and uniformly in all EU member states without needing national implementing measures, establishing common rules and standards across the Union.
-
D.
European company
A European company is a business entity legally registered and operating within one or more countries of Europe, subject to European and relevant national regulations, markets, and cultural contexts.
-
E.
company law
Company law is the body of legal rules and principles that governs the formation, operation, management, and dissolution of companies and the rights and duties of their stakeholders.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:56 p.m.