Triple
T15967918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of State of Bulgaria |
E387241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial-administrative body |
C2308
|
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: judicial-administrative body Context triple: [Council of State of Bulgaria, instanceOf, judicial-administrative body]
-
A.
Judicial body
A judicial body is an official group or institution empowered by law to interpret and apply legal rules, resolve disputes, and administer justice.
-
B.
quasi‑judicial body
chosen
A quasi-judicial body is an administrative or regulatory entity that has powers and procedures resembling those of a court, enabling it to interpret laws, conduct hearings, and make binding decisions or recommendations in specific areas of public or private disputes.
-
C.
judicial administrative office
A judicial administrative office is an organizational unit within the court system responsible for managing the non-judicial functions of the judiciary, such as case processing, records management, budgeting, staffing, and overall court operations support.
-
D.
civilian administrative body
A civilian administrative body is a non-military organization responsible for managing public affairs, implementing policies, and providing governmental services within a defined jurisdiction.
-
E.
judicial appointments body
A judicial appointments body is an institution or committee responsible for selecting, recommending, or approving candidates for judicial office, often to promote independence, merit, and transparency in the judiciary.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:54 a.m.