Triple
T8055980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Slovenia |
E188001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical region of Slovenia |
C15419
|
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: historical region of Slovenia Context triple: [Southeastern Slovenia, instanceOf, historical region of Slovenia]
-
A.
traditional region of Slovenia
chosen
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.
-
B.
historical region of Slovakia
A historical region of Slovakia is a geographically and culturally distinct area within the territory of present-day Slovakia that has developed its own identity, traditions, and administrative significance over the course of history.
-
C.
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.
-
D.
historical region of Italy
A historical region of Italy is a geographically defined area that played a distinct political, cultural, or administrative role in Italy’s past, often predating or differing from the country’s modern regional boundaries.
-
E.
South Slavic state
A South Slavic state is a political entity whose core population, culture, and historical development are primarily associated with the South Slavic peoples of the Balkan Peninsula.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:25 p.m.