Triple
T25646819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Serbian Krajina |
E642986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Serb breakaway entity |
C50594
|
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: Serb breakaway entity Context triple: [Republic of Serbian Krajina, instanceOf, Serb breakaway entity]
-
A.
entity of Bosnia and Herzegovina
An entity of Bosnia and Herzegovina is one of the two main political-administrative divisions of the country, each possessing its own government, constitution, and significant autonomy within the sovereign state.
-
B.
Russian-backed separatist entity
A Russian-backed separatist entity is a breakaway political or military group that seeks to detach from its parent state and operates with significant political, financial, or military support from the Russian government.
-
C.
Serbian organization
A Serbian organization is a structured group or entity based in Serbia that coordinates people and resources to pursue specific social, economic, cultural, political, or charitable objectives within the Serbian context.
-
D.
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.
-
E.
Free Territory of Trieste
The Free Territory of Trieste was a short-lived, internationally administered city-state on the Adriatic Sea (1947–1954), created after World War II to resolve territorial disputes between Italy and Yugoslavia.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 5:55 p.m.