Triple
T29384587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | administrative courts of Ukraine |
E745217
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized courts |
C767
|
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: specialized courts Context triple: [administrative courts of Ukraine, instanceOf, specialized courts]
-
A.
special court
chosen
A special court is a judicial body established to handle specific types of cases or issues outside the jurisdiction or procedures of ordinary courts, often with specialized rules, judges, or limited subject matter.
-
B.
specialized court registry
A specialized court registry is an administrative office within a particular type of court (e.g., family, commercial, or tax court) responsible for managing case filings, records, scheduling, and procedural documentation specific to that court’s jurisdiction.
-
C.
Designating authority for special courts
The designating authority for special courts is the entity legally empowered to establish, appoint, or assign judges and jurisdictions to specialized judicial bodies for handling particular categories of cases.
-
D.
subdivision of court
A subdivision of court is a distinct organizational unit within a larger judicial system, defined by specific jurisdictional scope, case types, or geographic boundaries.
-
E.
court music
Court music is a genre of music composed and performed specifically for royal or noble courts, often serving ceremonial, entertainment, and representational functions within aristocratic or monarchical settings.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:37 p.m.