Triple
T33699263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SI-112 (Municipality of Sevnica) |
E863408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slovenian municipality code |
C59202
|
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: Slovenian municipality code Context triple: [SI-112 (Municipality of Sevnica), instanceOf, Slovenian municipality code]
-
A.
Slovenian statute
A Slovenian statute is a formal written law enacted by the legislative authority of Slovenia that establishes, modifies, or regulates legal rights and obligations within the country’s jurisdiction.
-
B.
statistical region of Slovenia
A statistical region of Slovenia is an administrative territorial unit used primarily for collecting, analyzing, and presenting regional statistical data and for planning regional development policies.
-
C.
county of Croatia
A county of Croatia is a primary administrative and territorial unit of the country, governed by a county assembly and prefect, responsible for regional self-government, public services, and coordination of local municipalities and cities within its borders.
-
D.
Slovenian government body
A Slovenian government body is an official public institution or agency established by the Republic of Slovenia to perform specific administrative, regulatory, legislative, or judicial functions within the national governance framework.
-
E.
traditional region of Slovenia
A traditional region of Slovenia is a historically and culturally defined area whose boundaries reflect long-standing social, linguistic, and regional identities rather than current administrative divisions.
- F. None of above. chosen
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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.