Triple
T10757842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staff Regulations of the Council of Europe |
E253746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative law instrument |
C10533
|
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: administrative law instrument Context triple: [Staff Regulations of the Council of Europe, instanceOf, administrative law instrument]
-
A.
administrative instrument
chosen
An administrative instrument is a formal tool, document, or mechanism used by an organization or authority to implement, manage, or regulate administrative processes and decisions.
-
B.
administrative authority
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
-
C.
administrative law case
An administrative law case is a legal dispute that arises from actions or decisions of government agencies, focusing on the interpretation, application, or validity of administrative rules and procedures.
-
D.
branch of administrative law
A branch of administrative law is a specialized area within the broader field that governs the organization, powers, procedures, and accountability of public administrative agencies in a particular domain (such as environmental regulation, immigration, or social welfare).
-
E.
administrative obligation
An administrative obligation is a duty imposed on individuals or organizations to complete specific formal procedures, filings, or compliance tasks required by governing authorities or institutional rules.
- 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.