Triple
T23860620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federation of Bosnia and Herzegovina and Republika Srpska (condominium) |
E592437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | territorial arrangement |
C20214
|
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: territorial arrangement Context triple: [Federation of Bosnia and Herzegovina and Republika Srpska (condominium), instanceOf, territorial arrangement]
-
A.
territorial relationship
chosen
A territorial relationship is a conceptual association that defines how entities claim, control, share, or interact within a specific geographic or spatial area.
-
B.
territorial designation
A territorial designation is a formal label or title that identifies and defines a specific geographic area or jurisdiction for political, administrative, or legal purposes.
-
C.
territorial land apportionment register
A territorial land apportionment register is an official, systematically organized record that defines and catalogs the division of a country’s territory into administrative and statistical units for governance, planning, and data management purposes.
-
D.
territorial possession
A territorial possession is a geographic area under the authority and control of a state or sovereign power, typically lacking full political integration or equal status with the controlling entity’s core territory.
-
E.
territorial acquisition
Territorial acquisition is the process by which a state or entity gains control over land or geographic space through means such as conquest, cession, purchase, occupation, or accretion.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 8:12 p.m.