Triple
T4083298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autonomous Province of Vojvodina |
E87528
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous province |
C2839
|
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: autonomous province Context triple: [Autonomous Province of Vojvodina, instanceOf, autonomous province]
-
A.
autonomous prefecture
An autonomous prefecture is an administrative division granted a degree of self-governance, typically to recognize and accommodate the political, cultural, and linguistic rights of a specific ethnic or regional minority group within a larger state.
-
B.
island province
An island province is an administrative region consisting entirely of one or more islands, geographically separated from a country's mainland but governed as an integral part of the national territory.
-
C.
island province
An island province is a territorial and administrative division of a country that consists entirely of one or more islands, often with distinct geographic, cultural, and economic characteristics shaped by its maritime setting.
-
D.
autonomous region of China
An autonomous region of China is a first-level administrative division granted a degree of self-governance and cultural autonomy, typically in areas with significant ethnic minority populations.
-
E.
self-governing territory
chosen
A self-governing territory is a geographically defined area that exercises autonomous control over its internal affairs under its own local government, while remaining formally subject to a larger sovereign state.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.