Triple
T29384403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Administrative Court of Ukraine |
E745212
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high specialized court of Ukraine |
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: high specialized court of Ukraine Context triple: [High Administrative Court of Ukraine, instanceOf, high specialized court of Ukraine]
-
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.
supranational court
A supranational court is a judicial body established by multiple states or international organizations with authority to interpret and apply shared legal norms and issue binding decisions that transcend individual national legal systems.
-
C.
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.
-
D.
hromada of Ukraine
A hromada of Ukraine is a basic unit of local self-government, typically comprising one or several settlements that jointly manage local administration, services, and development.
-
E.
sovereign court
A sovereign court is the highest judicial body of a sovereign state, vested with ultimate authority to interpret its laws, resolve major legal disputes, and often review the actions of other branches of government.
- 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.