Triple
T10757840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staff Regulations of the Council of Europe |
E253746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | staff regulations |
C20083
|
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: staff regulations Context triple: [Staff Regulations of the Council of Europe, instanceOf, staff regulations]
-
A.
service regulations
Service regulations are formal rules and guidelines that govern the provision, quality, procedures, and responsibilities associated with delivering a particular service.
-
B.
military regulations
Military regulations are formal, authoritative rules and directives that govern the conduct, organization, procedures, and responsibilities of armed forces personnel and operations.
-
C.
safety regulation
A safety regulation is a formal rule or standard established by authorities or organizations to prevent harm, reduce risk, and protect people, property, and the environment in specific activities or industries.
-
D.
central government regulations
Central government regulations are legally binding rules and standards issued by national authorities to direct, control, and coordinate activities within a country in accordance with public policy and law.
-
E.
regulatory provision
chosen
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:15 p.m.