Triple
T4083299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autonomous Province of Vojvodina |
E87528
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | first-level administrative division of Serbia |
C740
|
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: first-level administrative division of Serbia Context triple: [Autonomous Province of Vojvodina, instanceOf, first-level administrative division of Serbia]
-
A.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
B.
constituent republic of Yugoslavia
A constituent republic of Yugoslavia was a federal unit within the Socialist Federal Republic of Yugoslavia that possessed its own government and constitution while remaining subordinate to the federal authorities.
-
C.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
D.
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.
-
E.
administrative territorial entity
chosen
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
- 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.