Triple
T2043437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucania |
E45396
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical region of Italy |
C9370
|
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 Italy Context triple: [Lucania, instanceOf, historical region of Italy]
-
A.
former province of Italy
A former province of Italy is an obsolete administrative division that once functioned as a mid-level local government unit within an Italian region, typically encompassing multiple municipalities before being reorganized or replaced.
-
B.
metropolitan city of Italy
A metropolitan city of Italy is a large urban area and its surrounding municipalities governed as a single administrative entity with special powers for planning, infrastructure, and local services.
-
C.
country in Central Europe
A country in Central Europe is a sovereign state located in the central part of the European continent, typically characterized by its landlocked or partially landlocked position and cultural, historical, and economic ties with neighboring European nations.
-
D.
historical province of Japan
A historical province of Japan is a former administrative and geographic division that existed before the modern prefecture system, often retaining cultural and historical significance in regional identity.
-
E.
Italian comune
An Italian comune is the basic administrative division in Italy, equivalent to a municipality, responsible for local governance, public services, and community regulations within its defined territory.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:39 p.m.