Triple
T10342170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Employment Guidelines |
E243151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU soft law measure |
C4537
|
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 soft law measure Context triple: [Employment Guidelines, instanceOf, EU soft law measure]
-
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.
soft law instrument
chosen
A soft law instrument is a non-binding agreement, guideline, or standard that influences behavior and shapes legal expectations without having formal, enforceable legal force.
-
C.
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.
-
D.
European Union convention
A European Union convention is a formal international agreement between EU member states, or between the EU and other parties, that establishes common rules, standards, or cooperation frameworks in specific policy areas.
-
E.
European Union policy framework
The European Union policy framework is the overarching system of treaties, institutions, laws, and coordinated strategies through which EU member states collectively design, implement, and enforce policies across economic, social, environmental, and security domains.
- 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.