Triple
T5872982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EC) No 851/2004 |
E130561
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU secondary law |
C14089
|
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 secondary law Context triple: [Regulation (EC) No 851/2004, instanceOf, EU secondary law]
-
A.
EU legal act
chosen
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.
European Union regulation
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.
-
C.
Italian law
Italian law is the legal system of Italy, rooted in Roman law and codified civil law traditions, governing public, private, and criminal matters through a hierarchy of constitutional, statutory, and regulatory norms.
-
D.
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.
-
E.
Swedish law
Swedish law is the body of legal rules and principles governing Sweden, encompassing its constitution, legislation, case law, and administrative regulations that regulate public and private life within the country.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:56 p.m.